Yeah, HeliBoard or FlorisBoard would’ve been my recommendation. They’re very similar, though (and presumably share most code between themselves).

Multiple people have said that, yeah. But they also said that he did not particularly distance himself from the project, which is definitely something I would do, if I found out about this kind of backing.

Believe what you want, but Drew DeVault has more of a reputation than FUTO.

From a communication viewpoint, that is fair, but to my knowledge (from being a professional software developer), effectively any license that is not ‘open-source’ or ‘free’ is by definition proprietary.

Because those two terms describe licensing standards (the only established ones that I know of). Whereas I believe, “proprietary license” uses this meaning of proprietary:

Nonstandard and controlled by one particular organization.

So, they wrote that license themselves is the point. What it says in there is secondary in meaning.

This is so highly relevant because in legal disputes, there is certain license compatibilities which are known to be possible.
You can take a library licensed under the MIT license and use it in a project that uses the Apache-2.0 license and you’re perfectly fine. This is the foundation of why the open-source ecosystem exists at all.

But you cannot take the source code from FUTO and use it in a differently licensed project, because no legal precedents exist to support this. (I believe, the FUTO license also actively prohibits this in some way, but that’s beside the point.)
This has massive implications. Like, yeah, you can look at the code, but it is useless. If FUTO closes shop or enshittifies, you cannot fork their projects.
And because you cannot legally re-use their source code in other projects, likely no one looks at it in depth either.

Damn, I’ve had technological disagreements with Mr. DeVault in the past. Obviously, I did not assume those to mean I’d disagree with him on everything, but it still feels surreal to read an entire post where I’m fully on board with everything he writes (and appreciate all the info I did not know).

Cool to see that he’s fighting the good fight.

Yeah, that’s so ridiculous. They could’ve just turned off the heating and made it lay flat, and it would’ve been fine. But evidently, they did not even think about handling an outage.

I’d argue that it’s Android’s DE for Linux.

Works fine for me. ¯\_( ᵔ ~ ᵔ )_/¯

A colleague always complains that KDE looks like Windows. She does also get jealous, though, when she sees me using poweruser features.

Yeah, for me it’s not even just the creative freedom, but an actual fuzzy feeling that me and the devs are having fun together. Open-source games also hold a special place in my heart for that reason, no matter how scrungy they are.

Yeah, I might be showing my age, but my interpretation of “a better game” was right away “a more fun game”, which got followed up with the thought: Did it make them more fun?

I feel like we had fun figured out pretty well in the last century already. And in many ways, the higher specs are used to add realism and storytelling, which I know many people enjoy in their own way, but they’re often at odds with fun, or at least sit between the fun parts of a game.

Like, man, I watched a video of the newest Pokémon game and they played for more than an hour before the tutorial + plot exposition was over. Practically no fun occurred in that first hour.
Just imagine putting coins into an arcade cabinet and the first hour is an utter waste of time. You’d ask for your money back.

There’s no way they actually checked that it works. It includes code for:

• XDG
• GNOME
• “GNOME_old”
• KDE

Verifying this would mean logging into several different desktop environments.

It’s also extremely fragile code, running external commands and filtering through various files. There just is no good API on Linux for querying whether the desktop environment is using a dark theme, so it’s doing absolutely inane shit that no sane developer would type out.

Because it’s a maintenance nightmare. Because they almost certainly don’t actually need to solve this. That’s software development 101, to not write code that you don’t actually need. But apparently some devs never got the memo that this is because of the maintenance cost, not because you weren’t able to generate the code up until now.

Typically, touchpad gestures (particularly multi-touch gestures) will work better on Wayland, because it has libinput.

Yeah, it’s explicitly built to run in a browser: https://agama-project.github.io/

I guess, the idea is mainly that you can also perform the installation over the network. I can imagine this being quite cool for setting up a Raspberry Pi or similar.

Non-GitHub changelog: https://fishshell.com/docs/current/relnotes.html#fish-4-1-0-released-september-27-2025

The default on Fedora is btrfs, which sounds like what OP is using.

Are there other types of people? Writing software to be bug-for-bug compatible with something else is really difficult and, yes, not fun at all. You will not find many people looking to volunteer for that…

Well, there’s a separate technology stack for virtualization. So, it would be similar in effect, but the way you get there is different, and it’s possible that it performs better or worse for certain scenarios.

That’s kind of hilarious. At first we had VMs to run entirely separate operating systems. Then we had Containers to separate everything except the kernel. And now we might get separation for just the kernel.