It…seems like there may be some issues with the repo…

That’s a fair point. I’ve always assumed it was a form of rate-limiting, but you’re right, that’ll be part of their analytics at least

Oh, whoops! I didn’t notice its timestamp when I read it 😅

I don’t hate YAML, but it has the same issues languages like PHP and JS introduce…there are unexpected corner cases that only exist because the designer wanted the language to be “friendly”

https://www.bram.us/2022/01/11/yaml-the-norway-problem/

For what it’s worth, I have been a convert from naive to aware for a couple years now. I used to like to think naive == UTC, but when data comes from unverifiable sources, you can’t know that for certain…

Yes, testing infrastructure is being put in place and some low-hanging fruit bugs have already been squashed. This bodes well, but it’s still early days, and I imagine not a lot of GIL-less production deployments are out there yet - where the real showstoppers will potentially live.

I’m tenatively optimistic, but threading bugs are sometimes hard to catch

I’m curious to see how this whole thing shakes out. Like, will removing the GIL be an uphill battle that everyone regrets even suggesting?Will it be so easy, we wonder why we didn’t do it years ago? Or, most likely, somewhere in the middle?

If “build the server and client in the same language” is a hard requirement, I believe your only choice is JavaScript…

The tone of the post makes me think you’re newer to programming, so I’ll leave it at that, as extensions to this question can overwhelm quickly, but yeah, JavaScript is a fine language for what you’re doing

Putting aside the “should/shouldn’t do” argument, I was also wondering if the code is even viable. I imagine that ‘ls’ and ‘sudo’ are probably pretty ubiquitous, but I bet there exist some Linux installs out there with a different shell than ‘bash’, and some might not have ‘grep’ too. That would lead to some pretty cryptic bugs for the end user, eh?

What a strange article. The reasoning for why 22 is interesting though very straightforward, and the rest of the article is essentially “I asked for port 22, and they gave it to me”. Little fanfare, little in way of storytelling conflict.

Not an issue in and of itself, but strange with a title of the form “This is the story of…” That sort of titling usually begets intrigue and triumph over adversity, dunnit?

Yeah, I’ve implemented OTP before, and I can think of no way this could be a surveillance move. If they required you use their app because they use a custom solution, sure, maybe, but they’re OTP is currently entirely standard, so you can use a plethora of app (or roll your own in about 14 lines of Python)