This reminds me of a similar experience.

The first release of WSL(2) 1.0 (this versioning alone is worth another post here, but let's not talk about it) have its CLI --help message machine translated in some languages.
That's already evil enough, but the real problem is that they've blindly fed the whole message into the translator, so every line and word is translated, including the command's flag names.

So if you're Chinese, Japanese or French, you will have to guess what's the corresponding flag names in English in order to get anything working.
And as I've said it's machine translated so every word is. darn. inaccurate. How am I supposed to know that "--分布" is actually "--distribution"? It's "发行版" in Chinese and "ディストリビューション" in Japanese.

At last I had to switch my system language to English to set a WSL instance up. From then on I never use any display language other than English for Microsoft products. Sometimes "translated" is worse than raw text in its original language.

Related links if you like to see people suffer:
https://github.com/microsoft/WSL/issues/7868
https://github.com/microsoft/WSL/issues/4111

PS: for the original post, my stance is "please don't make your software interface different for different languages". It's the exact opposite of the author has claimed: it breaks the already formed connection by making people's commands different.
It's the CLI equivalence of scrambling every button to make sure they are placed differently in different languages in GUI. I hope this sounds stupid enough so that no one will try it.
A not-so-stupid way that I can think of is to add a "translation" subcommand to the app that given any supported flags in any language it converts them to the user's language. Which is still not so useful and is not any better than a properly translated documentation, anyway.

1. breaks compatibility
2. breaks compatibility
3. breaks compatibility
4. hard to add without breaking compatibility

Then we arrive at Rust as a natural outcome.

And it's of course possible to migrate to Rust from C or C++ progressively, fish has almost got it done.

Compared to btrfs it's claimed to be faster and having working RAID support. Its unique feature is using a fast device as cache to speed up access to slower, larger disks, I think.

It runs in the kernel of the OS as a driver, which means that it's basically a trusted malware that has even higher permission than the admin of the computer, and have access to more things than yourself, to closely monitor the whole system in order to find signs of cheating.

Honestly I'm surprised that so many people don't know how git can be used without those repository hosting sites. That's one way to use it, not the only way. And it's not even the way it was originally designed for.

Checkout git format-patch.

Git and Email are not mutually exclusive. In order to collaborate with git, you need and only need a way to send your commits to others. Commits can be formatted as plain-text files and sent through emails. That is how git has been used by its author from literally the first release of it.

Some have better ux, some support more platforms out of the box. I don't find it a good idea trying to replace everything though.

I'm looking forward to it.

On the technical side, they are using pure Rust to build the DE, and the Rust GUI ecosystem has been greatly improved by their hard work. If their product turns out to be successful, Iced may eventually become "the Qt of Rust".

As a user I like their design shown in current demos, and a Wayland-first DE with first class nvidia support is really needed.

the developer chooses to work with these publishers beforehand

What kind of paradise are you living in?

mindlessly chanting “tools”

That's what you were doing in the first place. Instead of evaluating and trying new things, you are putting them in an imaginary cycle, ignoring any actual value that they brings.

Also Rust has been on your "stage 2" for 10 years. It's now widely used in multiple mainstream operating systems for both components and drivers, driving part of the world's internet stack, and is used to build many of those "shiny and new tools".

So why not just use the lean and maintainable wlroots

wlroots can't be used (comfortably and idiomatically) in Rust because it's too hard (if not impossible) to provide a memory-safe interface for it.

we can move to another implementation of the Wayland protocols.

So unfortunately this has already happened.

I assume that you do know that tools improve objectively in the cycle and are making a joke on purpose.

KDE Plasma 6 for the resolution of so many issues; COSMIC DE as a brand new choice in the future; Guix System to have KDE and more packages shipped because it's literally the best designed distro as of now.

Is it truly free and open source?

Yes, both podman and podman-desktop are FOSS under Apache-2.0 license. And they prefer more open image hosts like quay.io by default (dockerhub is still available OOTB for it to be a drop-in replacement of docker)

Does it run only in Linux?

No, it runs on Linux, Windows and MacOS (through VMs on the latter two) and my experience is that it works better than docker on non-Linux machines.

When Windows decided to auto update in the middle of an important meeting without any prompt;
when I download files overnight and the fan takes off at midnight by its telemetry process;
when it gives me a full screen ad trying to change my system settings and stops me from entering the system on time;
when the system starts to integrate with ads from the browser to the taskbar.
It's not because how good Linux is, it's because how bad Windows has become.

So I left after my little checklist of must-to-haves is fulfilled. With no regrets.

Guile and Guix is way better documented than Nix. The language have more features, so you don't have to use a hack to load packages, can actually know what is accepted in a function instead of blindly copying what others do, and it comes with a formatter.

Any stream content. Any subscription. Anything that I can't access because of my nationality.

I'd pay for other things.

You can swap it with the standard one. It's on another non-official channel called nonguix.

Note that skim performs worse than fzf. There's a new matcher in Rust called nucleo which is faster, but it currently doesn't have a cli and can only be used inside Helix editor (hx)

nu is probably the best shell for ad-hoc data processing, handling all my daily needs in one expression.

fd and rg have another thing in common, that they're both 50% shorter than their traditional alternatives /s

If it's only for 3 days you need nothing unless you get diarrhea.