Less pithy, i seem to recall many issue with programs that relied on suid and permission dropping, which would be the 'oldschool' way of firming up the above.

You're not wrong that complexity has been introduced, and I'm not a a fan of snap either, but ultimately sandboxes (esp backwards compatible ones that don't need source level modifications) are complex.

If you want simple and secure, you're probably looking at OpenBSD and pledge.

Vega/VGlite have amazing charting expressivity in their spec language, most other charting libs don't come close. It would be very cool to be able to take advantage of that.

As a Go dev, I'm looking at this article with great interest. I would very much like to apply this approach to Go as well, I think the author has got a very strong design there.

E.G. can you set one screen to 150% and one to 175%? (I think the answer to this is 'technically yes but then everything goes a bit blurry because they do it by rendering at 2x then downscaling')

Proper mixed dpi scaling means stuff will render pixel-perfectly instead of downscaling hacks.

This makes it very difficult for Wayland to evolve in a way that people want, as Gnome is the biggest player by user count.

Flatpak is installed by default and used by their app store, and Firefox is packaged as a deb so you can avoid the snap.

I consider it a deshittified Ubuntu.

How do the big Unicode OSS fonts like Noto, Deja Vu deal with this?

Even so, latency-in-zoom kind of becomes an attribute of the medium and you learn to adapt. How does it feel with the Vision Pro though? The article talks about a really convincing sense of being in the same place with someone - how does latency affect that? (And does it differ based on if you're all physically in Silicon Valley or not?)