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…

I read elsewhere that it’ll have anti-cheat. If they don’t support Linux, anti-cheat will make it rather unlikely to work, since it will detect the mild differences between Proton and Windows as an attempt to cheat.

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…

I started noticing it around February or March or so.

I feel like it’s displacing Corporate Memphis, at the very least in terms of how much I hate it.

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.

Yeah, those models are referred to as “discriminative AI”. Basically, if you heard about “AI” from around 2018 until 2022, that’s what was meant.

Yeah, there were also several stories where the AI just detected that all the pictures of the illness had e.g. a ruler in them, whereas the control pictures did not. It’s easy to produce impressive results when your methodology sucks. And unfortunately, those results will get reported on before peer reviews are in and before others have attempted to reproduce the results.

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.

(saying something more realistic like “2015” or whatever your inexperience or AI told you to)

User input is probably the big one where this API is gonna get stress-tested…

Hmm, I can believe that it was based on java.util.Date, but I don’t remember that being as unpredictable. I guess, a different API to begin with, would have avoided a lot of problems, though…

I do enjoy the irony of them ignoring that particular social cue. 🙃

“Elmer’s” is a glue manufacturer, for others wondering: https://en.wikipedia.org/wiki/Elmer’s_Products

For testing new speakers, this song: http://dig.ccmixter.org/files/Robbero/59698