Part of me wonders how much of this is hardware vendors releasing unusable hardware. I don't know what the hangup on the RPi is (that seems odd, given how prevalent Linux on the RPi is) but that & the keyboard RGB LEDs seems like your bog standard "the hardware can't or if it can, the vendor didn't bother to document anything". The FOSS world has done an incredible amount of work reverse engineering over the years, but the behavior of HW companies are more to blame, and that's not a problem you'll solve with tech.<p>But hardware vendors have for years, and still do, just say "our use case, or the highway, you don't really own the thing you're buying." And there's not much out there for one to "vote with one's wallet" on it.<p>"FS can't store a file in two spots" … I want to accuse OP of being a Windows user, but they're obviously not [only]. So that's … an odd critique?<p>I still think hierarchical+symlinks beats trying to tag stuff, and I've lived through enough decades of AI trying to tag stuff and deciding things like that Mozart is "Rap [explicit]". I don't have the mental capacity for it. Just give me the dumb hierarchy with (sym)links. (And bind mounts.) (But I wouldn't oppose an OS trying it.)<p>"Let's ditch all IPC" … buuuut adds IPC right back in. Okay :). I suppose it's "only message passing". (And I do think message passing is a great default, and what most things need.)<p>"Native apps are bloated". The most bloated apps I have are all the Electron ones. I don't think most people are concluding this...<p>I'd love a multi-item clipboard, but the devil is in the details: sensitive items and large transfers.<p>> <i>it's the pure text nature that bothers me. Instead of chaining CLI apps together with text streams we need something richer, like serialized object streams (think JSON but more efficient).</i><p>You have to consider the bulk cases. But very much yes; I wish at least that Unix had settled on <i>typed</i> bytestreams, like MIME+stream, and some form of content negotiation. Unix scripts are rife with examples of `a | b` where a & b speak different formats and I feel like it took forever to get good tooling around strongly specified formats (instead of just bullshitting with awk/grep/cut/tr/etc.) with tools like jq, yq, xsv, etc. I just wish applications could just have a means to understand "oh, I'm getting this kind of data" or "I have no idea what this is, and I shouldn't just GIGO".<p>> <i>In our new OS every window is tab dockable. Or side dockable. Or something else</i><p>Have you tried a tiling WM?<p>If you design an OS ... make the FS Unicode only, and ban "\n" from filenames. Life will be simpler.