It’s not about the bindings. It’s, as always with kernel devs, about gatekeeping and unprofessional if not outwardly hostile behavior.

Maintaining bindings is a hard problem for sure, but no hard problems have ever been solved by the key stakeholders refusing to partake in honest discussions. Asahi Lina’s breakdown of her rejected contributions to the fundamentally flawed drm_sched, which do not involve a single byte of Rust, demonstrates an unwillingness to collaborate that goes much further than the sealioning about muh bindings.

I don’t agree. If anything right now we have the opposite problem where the English world for instance pretty exclusively uses a more than 500 year old translation of the Bible, despite much more modern-English versions being translated from some very early Greek versions of the texts (therefore being more readable and less telephone-y). The reasons for the KJV being preferred are many but none make any real theological or linguistic sense.

What really happens though is not so much a game of telephone than the fact that every culture gets to decide on its own (usually provably incorrect and inconsistent) interpretation of the texts, because the whole thing is so internally inconsistent it’s basically a Rorschach test no matter which way you translate it. Progressive Christians will basically tell you that literally none of the Old Testament is to be taken literally which… okay? Extremists sects will do the opposite. Then there’s the whole dogma around Lucifer and Hell, whose existence is clearly an inconsistent amalgamation of old polytheist religions and no matter which way you read or translate it doesn’t translate to the Lucifer or Hell that most Christians ever think about when they say “Lucifer” and “Hell”. That part was just straight up made up over the centuries because it was a convenient scarecrow, yet is is absolutely load-bearing to the dogma of almost every Christian sect. And let’s not even get into the feminists and queer people who’d put Simone Biles to shame with their mental gymnastics justifying the Bible being an Ally, Actually™. That’s not a game of telephone, that’s just Weapons of Mass Denial.

If anything i18n makes things way worse for everyone. Ever tried to diagnose a semi-obscure Windows or Android error on a non-English locale? Pretty sure that’s one of the activities in the inner circles of Hell. Bonus points if the error message is obviously machine-translated and therefore semantically meaningless.

Unique error codes fix this if they remain visible to the user, which they usually don’t because Mr Project Manager thinks it looks untidy.

You’re describing proper incident response but I fail to see what that has to do with the status page. They have core metrics that they could display on that status page without a human being involved.

IMO a customer-friendly status page would automatically display elevated error rates as “suspected outage” or whatever. Then management can add more detail and/or say “confirmed outage”. In fact that’s how the reddit status page works (or at least used to work), it even shows little graphs with error rates and processing backlogs.

There are reasons why these automated systems don’t exist, but none of these reasons align with user interests.

It goes deeper than parents being nostalgic. The veneer of meritocracy is load-bearing to neoliberal ideology, especially post-WWII. If we, as a ~society~, acknowledged that no matter how big kids dream and how much they work they’ll probably never make it more than maybe one or two steps up the social ladder, our entire social model would collapse.

At its most fundamental level, that’s what the war against “wokism” is. It’s the privileged correctly identifying and targeting the existential threat that is the mere acknowledgement that we do not live in a meritocracy.

Having to behave around psychiatrists like one would around the fucking police is incredibly problematic. I can’t even express how secondhand-frustrated this post and your comment make me.

Psychiatrists are supposed to evaluate someone’s mental state, sometimes with full power over someone’s access to healthcare, freedom or (in some US states) life, and they can’t be trusted to recognize a joke when they hear one?

There are two kinds of powerusers, and they DO NOT understand each other one bit.

The first, like you, just wants to get shit done and want to avoid the friction of choosing/installing/configuring their tools. GNOME, Chromium, and VSCode will do just fine.

The second, like me, wants to get shit done as well, but has a strong need for a very specific workflow. I’ll spend half an hour to get a toolchain working on nvim instead of using a pre-baked VSCode plugin. Not because VSCode is bad, but because I have a very (!) specific workflow and associated muscle memory and anything else distracts and unsettles me.

Some of the best engineers I know fall into either category, neither way is superior it’s just how brains are wired.

Anyway I use Kitty because it allows me to split tabs into windows (not windows into tabs! ew!), has low latency with high throughput thanks to GPU rendering, and a low memory footprint.

mentally stable

anakin-padme.jpg

You mean npm duplicates even if the the two dependency versions are compatible?

By default yes, unless you explicity use the “peer dependency” system which isn’t the default. The “default” naive implementation is for every package in your node_modules to have a node_modules of its own, all the way down recursively. There are tricks nowdays to deduplicate packages with the exact same version, but not to automatically detect “compatible” versions and use those instead (in my experience nothing would work if that was the case, deleting package-lock.json causes way too many issues due to the… uh, let’s call it “brave” approach of JS devs to stability).

That couldn’t be, right? Otherwise, if you installed two packages that rely on different incompatible versions of another package, one of the two would break

Correct. This is intended behavior which is solved in several ways:

1. Correctly declaring your dependencies. If newer versions of a dependency break your package, disallow them, but that is not normally needed for minor version changes.
2. Focus on quality. Semver exists for a reason, and 1.2.3 should not break something built against 1.1.2. JS and NPM’s cascade of stupid implementations bred a culture of “move fast and break things”, but that’s not the norm in any other commonly used ecosystem
3. Linux distros almost exclusively use curated repositories, so they are (mostly) internally consistent and incompatibilities are rare and quickly fixed. A good package manager will resolve dependencies and automatically detect incompatibilities, proposing several fixes (typically abort the upgrade or uninstall one of the problematic packages)
4. Not breaking down packages into a constellation of smaller packages. glibc6 is glibc6, not glibc_string (1.2.3) + glibc_memory (2.6.5) + glibc_fs (1.5.3) + glibc_stdio (1.9.2) + glibc_threads (6.1.0) + …
   Internally glibc6 is a bunch of modules, but they get bundled into one package specifically to simplify dependency management.

Not being able to install two versions of the same package sounds restrictive, but it’s a HUGE security benefit: glibc6 (1.2.3) is vulnerable to CVE-2024-1, then updating to glibc6 (1.2.4) secures your entire system at once. With NPM though, you have to either wait for every. single. dependency on that vulnerable package down your tree to recursively update, or patch those versions yourself (at your own risk because again, small version changes often break things since developers think that NPM’s dependency model means they don’t have to actually provide stability guarantees).

It’s saner, not perfect. With virtualenvs it does basically what you describe except that it re-downloads everything for every virtualenv, but that does not typically matter much since it’s not downloading a billion dependencies.

With NPM there’s no choice but to have hundreds of duplicates installed for every project, that’s not just inefficient but it is a security, maintainability, and auditability nightmare.

You’re answering an argument I didn’t make. I’m just pointing out that these arguments about “legality” and “legitimacy” in Yemen are stupid as fuck. There is an internationally recognized government, which supports bombing operations but doesn’t control most of Yemen which is controlled by the Houthis, which supposedly support Palestine but in practice are just theocratic Iranian puppets.

Claiming that one is “legitimate” is a political act, and maybe we could be honest about that for five seconds instead of flip-flopping between the two depending on who’s being oppressed.

npm downloads every dependency recursively. If a depends on d (= 1.2.3) and b depends on d (= 1.2.4), then both versions of d get downloaded into a and b’s respective node_modules.

All other package managers I’m aware of resolve dependencies into a flat list then download, and you can only have one version of the same package on your system.

1. Like Python, have a large and featureful standard library such that > 80% of NPM packages are redundant. Other languages allow you to make very large projects with only a few tens of dependencies. JavaScript requires THOUSANDS.
2. With this in place, stop with the recursive dependencies, immediately and forever. Every other package manager under the sun installs the dependencies next to each other.

I’d say pip is saner, though not by much as its support for private registries is very bad and seems designed to facilitate supply-chain attacks. I’ve heard a lot of good things about cargo but haven’t used it enough myself to have a strong opinion.

Yet when Biden bombs the Houthis, it’s “violation of international law” because the Houthis are the “de facto government of Yemen”. Or at least that was the consensus on Lemmy a couple months back.

Like, I don’t really care. Fuck the Houthis and fuck Israel. But it’s interesting how the Lemmy hivemind picks and chooses who is “the legitimate Yemeni government” based on their personal values.

I didn’t even BUY the damn game and the fact that you feel the need to say this regardless shows that the only thing you care about is virtue signalling. Congratulations on your moral high ground.

Believe me I know, I’ve been seeing this crusade for over a decade now (I think it was TotalBuiscuit who started it?).

However I do not see a reason to use such a dismissive tone when there is nothing in the article that implies that the customers were being “dumb” and pre-ordered or bought blindly.

Also this debacle definitely hurts CO&Paradox a lot more than they made in sales. Unlike a AAA from Ubisoft or the millionth over-marketed DayZ clone du jour, people who play strategy games do follow the gaming press so future sales will be impacted. In fact, EA conspicuously hasn’t released a new SimCity after 2013’s disaster (C:S surely played a role in this as well by releasing in 2015, but they wouldn’t have eaten up all the customer base if SimCity 2013 had been half as good as SimCity 4).

Yeah, and the people like me who haven’t bought it are pissed. That game had a lot of potential to fix C:S 1’s flaws, which was squandered to performance issues.

Buy the game, can’t complain because you are a filthy PrE-ORdErEr. Don’t buy the game, can’t complain because you didn’t buy the game. What kind of logic is that?

US-defaultism has a catch: it sometimes accidentally extends to the Commonwealth. You won’t run into most of the internationalization quirks if all you’re comparing is “British English vs American English”.
[Sidebar: I notice this also when English speakers online assume that their audience at least has a vague idea of what Imperial units are, but while that is true of most native English speakers in the northern hemisphere who use feet and miles colloquially, for ESL audiences it’s almost always incorrect]

I switched from AZERTY to US QWERTY permanently specifically to avoid all the issues of badly internationalized software. Bad default bindings (e.g. common vim operations like { requiring the use of AltGr), but also things like games not working at all or only partially (e.g. the number row being either unbindable, or key hints naively showing as “&” and “é” instead of “1” and “2”). Surprisingly few devs understand the difference between key codes and characters, and lots of indie games straight up don’t even internationalize and require switching layouts (good luck if there is an in-game chat).
After getting into mechanical keyboards, the ANSI US keyboard layout has been useful as well because these are quite common. ISO mechanical keyboards are rarer, and Belgian AZERTY keycaps are borderline nonexistent.

Also in practice I use the qwerty-fr layout which is the US layout with a French layer on AltGr. The kicker? It’s better at writing French than the French AZERTY which is missing a lot of letters (Ç, æ, œ, À, …). AZERTY is a terrible layout but that’s a separate discussion.

Of course the Americans should develop properly internationalized software, but I personally know several fellow Belgians who switched to QWERTY for (some of) the reasons outlined above.

The version that shipped with the disk? It’s not 2005 anymore gramps.

Either there’s no disk but a redeemable code (for a license), or there’s a disk but without even the day 1 patch (which requires a license and the game probably runs like shit without it).

Piracy is WAY superior in those aspects. At least a repack had all the game updates bundled in.

Removed by mod