Sure, I guess, if you’ve got a distro installed on your PC and use the distro-provided packages to install the Rust compiler, then you can’t be subject to such certificate MitM attacks.

Your comment sounded like you were primarily concerned about the shell script piping rather it just being a program which can be downloaded without going through distro packages.

You’re using that to download a program. If they can MitM the shell script, they can just as well MitM the program that you’ll run right after the download…

Anecdotal, but I actually stopped liking fictional stories at some point, because I realized there’s such an abundance of cool and real stories I could be learning about, that it’s just like “Why are you telling me of a phoenix/dragon/Lavados when there’s black hawks setting fire to Australia?”.

I guess, it also ties in, though, that I don’t do escapism in general either, so I don’t either get lost in real stories, nor drugs.
I had a rough point in my life where escapism was crucial – I certainly don’t judge anyone wanting to step outside of this world for some time – but yeah, that changed my fundamental world view, so that I prefer to stay in the real world now.

Are these genuinely just screencaps from Star Trek or something?

I guess, it being an identity is somewhat recent-ish…?

You first needed lots of weirdos to make it their identity that they only fuck people from the Champagne region, before it could be an identity that you just fuck whomever’s hot.

Well, the writing-part isn’t the bad part about duplicated code. It’s the maintaining of it. In particular, if you duplicate logic, it happens all too quickly that you make modifications to one, but not the other, or you make differing modifications to both.

Eventually, you’ll end up with two wildly different versions, where you won’t know why certain changes were made and not applied to the other version. Similarly, if you do need to make a similar change to both, you might now need to implement it two times.

I guess, I do agree that it isn’t *always* worth it, but in my experience, it is far more often worth it than one might think.

I genuinely get headaches from techno. A colleague was recently on a techno festival and that just sounds like the seventh circle of hell for me…

Can we at least mention, though, that that’s kind of nonsensical, too? Give me a *very* high-level summary of what changed, but then the rest of the commit message should be the why (unless that’s genuinely obvious, like when adding a feature).

If I actually want to know what changed, I can look at the code changes. I can’t find the why anywhere else, though. Nor can an LLM having to describe those random code changes.

I doubt it’ll be usable on most websites when they release their first version. It might take decades to support current web standards…

It’s a Linux concept. Basically, imagine you could have a Windows 11 PC with the Windows XP GUI or with the macOS GUI. In Linux, these kinds of different GUIs are just desktop environments, which you can install as you see fit.
Conversely, you can also have an OS without a desktop environment, which is basically what’s used on Linux server PCs.

Yep, the repository root. Where everyone starts to read your code, so you put your README there and the docs-folder and the entrypoint to your source tree, oh and also all this random guff that no sane reader would ever be interested in.

I still remember how I tried to read larger repositories for the first time and this was genuinely a hurdle, because I figured these files must be highly relevant for understanding the code.

My attempt at combating that has been to move as much of the code structure to the top as possible, so that someone new will have a much higher chance of clicking on something relevant. But yeah, downside is that your code structure isn’t as separated from the guff anymore…

Firefox has a built-in translation feature now, so you might not need TWP.

If you search for “find duplicate files <your OS>” there seem to be some options…

It was an effort by multiple Unix vendors to create a common desktop environment: https://en.wikipedia.org/wiki/Common_Desktop_Environment

*tabs Fedora*

I don’t have experience with Jujutsu, but I always have the same problem with these alternative frontends, which is that I’d still want to be proficient with the original. If you need to look up how to fix something or you want to help others in your team or you want to script something, then the language to speak is simply the Git CLI.

And I don’t feel like I even use the Git CLI enough where a different tool could be so much better that it’s worth learning both.
Obviously, your priorities may differ, but yeah, that’s just always the reason for me why I prefer the Git CLI, even if it were objectively more difficult to use.

I also enjoy “one”. There’s just a random “w” in there when you pronounce it.

We have a concept of word inflection, which can be used to replace a lot of words that English would use to denote something being a question, ownership markers, causes and effects etc.

I don’t speak Finnish, but I believe a good example for such an inflection is how in English you can glue an -s to words to make them plural. In some other languages, you say “many word” instead, because they don’t have such an inflection.

Hmm, what’s the berry he holds in his hand? I don’t think the others are poisonous, except maybe if you do eat them whole, then I don’t know…

It’s mainly horrid, because it means you have to code extremely defensively (or I guess, use a different API).
You can’t rely on new Date("not a date") aborting execution of your function by throwing an error. Instead, you have to know that it can produce an Invalid Date object and check for that. Otherwise a random NaN shows up during execution, which is gonna be extremely fun to try to find the source of.

I understand that it’s implemented like that partially for historical reasons, partially because it’s often better to display “NaN” rather than nothing, but it’s still the sort of behavior that puts me in a cold sweat, because I should be memorizing all kinds of Best Practices™ before trying to code JavaScript.