Overall, my Linux GUI experience has never been as smooth as it is now on Wayland and I tried pretty much all common DEs/WMs in last 8 years.
X11 is not even remotely close to being "there" compared to Wayland and if Gnome implementation sucks, then please first try better implementations first before writing comments like this.
No, Wayland protocol is not perfect and yes, some niche use cases are still not covered, which is why various extensions of the protocol are still being developed. X11 at it's current state is nothing but a collection of hacks glued together. Wayland is, however, a very robust, secure and well-designed modern protocol, which, most importantly and contrary to X11, actually works.
> 1. No matter what operating system you're on, you'll eventually run into an application that doesn't render in high dpi mode. Depending on the OS that can mean it renders tiny, or that the whole things is super ugly and pixelated (WAY worse than on a native 1080p display)
Never happened to me in 4 years, see below. That said, I barely use any graphical programs besides kitty, firefox, thunderbird and spotify.
> 3. Configuring my preferred linux environment to work with 4k is either impossible or just super time consuming. I use i3 and it adds way more productivity to my workflow than "My fonts are almost imperceptively sharper" ever could
This is just not true. I have used the same 32" 4k monitor for 4 years running NixOS with bspwm (a tiling window manager, which does even less than i3) on 3 different laptops - thinkpad x230 (at 30 Hz), x260 and x395 and it all worked completely fine.
It depends on a very simple tool I wrote, because I was sick with `xrandr`: https://github.com/rvolosatovs/gorandr , but `xrandr` could easily be used as alternative.
Recently I switched to Sway on Wayland and it could not be smoother - everything just works with no scripting, including hot-plug.
> I genuinely think 4k provides no real benefit to me as a developer unless the screen is 27" or higher, because increased pixel density just isn't required. If more pixels meant slightly higher density but also came with more usable screen real estate, that'd be what made the difference for me.
Indeed, screen size is way more important than resolution. In fact, even 4k at 27" seemed too small for me when I had to use that in the office - I would either have to deal with super small font sizes and straining my eyes or sacrificing screen space by zooming in.
Is a whole custom OS really necessary?
Couldn't you just simply use Mopidy(https://www.mopidy.com/)? Possibly with some additional plugins required to make it work for cars.
It runs on RPi and implements mpd protocol, hence, is fully compatible with mpd clients and has many more clients implemented targeting Mopidy itself.
Also, it plays music from Spotify, YouTube, SoundCloud and whatnot.
My reasoning is that it does one thing: Being a dumb head unit. Since it does just that one thing, it can be distributed as a big blob. You don't have to worry about changing that file or this file, following this instruction or that instruction, downloading this version or that version of the packages. It simplifies many things for the end user. I learned that from Retro Pie, a distro that I love.
Power users who want it to do many things can just run/read the scripts in the repo and make it a multi-purpose device. I'd imagine for $100 head unit, many people won't bother.
That being said, I really have to brush up on how to package Qt5 and OpenAuto as Debian packages.
I second this, especially since I have been burned by single-purpose raspberry "distros" multiple times in the past in the audio sector. Maintaince is more work than people often realise.
For example, here's an example of a Web App using [`wasi:keyvalue` interface](https://github.com/WebAssembly/wasi-keyvalue/) via WebTransport using wRPC: https://github.com/bytecodealliance/wrpc/tree/8e9de3b446ac05...
reply