I have a 12vdc direct power USBC charger for my tablet. This will totally fry any normal USBC device it touches.

can't say I have experienced that. I use a myriad of modern but lower end systems and stuff like dinit still uses less resources and is in turn better for the speed and responsiveness of my systems

this is pretty much how it works in some cases, you need to port from one protocol to another, or to a different system altogether.

I'm pretty sure everyone has settled by now, Personally I hate systemd. It's slow, relatively resource intensive, poorly designed in many aspects.

but as an init and service manager it's the best. Though I do have to say dinit does get pretty close for me now.

I personally use Arch on my desktop and artix on my laptop. I want Systemd to die just as much as the next Systemd hater, but unfortunately I don't believe we have anything better yet.

that's just the thing, This is again, more fragmentation, Some compositors support always on top, some don't, you choose x protocol for your app, and now your app works great on sway, but not on KDE or gnome, or it works great on gnome and not kde or sway etc. As an app developer the situation is a bloody joke. My current stance is "just use xwayland because wayland will never be suitable" and thankfully with cosmic and kde both supporting "don't scale xwayland" this seems to work well.

EDIT: they also make enough deviances from the upstream protocols that this can't really be considered a "experimental branch"

EX: https://github.com/misyltoad/frog-protocols/blob/main/frog-protocols/frog-color-management-v1.xml vs https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14/diffs

Yay, another set of protocols that will just lead to more and more fragmentation.

You do acknowledge one issue with Wayland, probably the biggest issue with Wayland, but then fail to acknowledge the second biggest issue with Wayland being fragmentation.

Solve one issue by making another issue worse.

this is from the google research team, they contribute a LOT to many foss projects. Google is not a monolith, each team is made of often very different folk, who have very different goals

Boring hit piece that way overblows some issues on the topic.

this is quite frankly, a really dumb picture that is wrong on many accounts

well this took literal years longer then I thought it would.

literally, all Chrome OS / chromium OS needs to do for me to actually embrace it. is native out of box flatpack support

one issue I might see them having with flatpack, is the permissions right now are handled kind of stupidly IMO. but if those get solved I think flatpack would be a great addition to chromium os ecosystem

all chromeOS needs to be immensely more useful is flatpak support, if chrome OS supported flatpaks directly, it could very well be my goto (well not chromeOS directly, probably thoriumOS) for older linux PCs for general populace