Yeah, if all those complainers want something more modular, they’re free to push for protocols that allow to leverage existing components while also allowing for them to come from multiple vendors.

Objectively, Apple is focusing on leveraging high DPI over subpixel tricks.

It makes sense that people who value sharpness on low DPI screens prefer subpixel rendering over grayscale.

https://kde.org/community/whatiskde/kdefreeqtfoundation/

Qt is a thing. Idk why all these environments are messing around with a GTK that’s being sabotaged/neglected by GNOME while Qt just keeps working.

Who?

A developer who hasn’t caught a virus since his teenage years.

Why would we?

Rust is faster than C. Iterators and mutable noalias can be optimized better. There’s still FORTRAN code in use because it’s noalias and therefore faster

You got it right, the person you replied to made a joke.

In a good way. Using a non-verified bytes type for strings was such a giant source of bugs. Text is complicated and pretending it isn’t won’t get you far.

I don’t think those are better or worse. My point isn’t about some ancient far too limiting standard, but about how easy it is to wreck everything by not knowing some obscure syntactical rule. My issue is about implicit conversion between strings and arrays, about silently swallowing errors and so on. And the only shell languages that I know aren’t idiotic are nushell and Powershell.

That KDE theme that nuked some user’s home directory? Used a bash script. That time the bumblebee graphics card switching utility deleted /var? Bash script. Any time some build system broke because of a space in a path: bash/ZSH/… script.

Why would anyone make an init system based on shell scripts these days?

POSIX shells are horrible unmaintainable bug factories.

shellcheck is not enough to make them safe programming languages. They are acceptable only in an interactive context.

Having anything encourage people to write POSIXy shell scripts is a design flaw.

Services are bash scripts?

Oh no. That’s horrifying. I’ll never go back to the bad old days where my system constantly has dozens of untestable buggy bash scripts running.

I currently have zero bash scripts running on my system until I open steam, and there’s no world where I’d go back.

No, because the kernel has a different goal than most other software. Linux agrees that breaking the userspace from userspace is sometimes necessary.

How is Arch “making things difficult for oneself”?

I set it up once 8 years ago and have since migrated my install across several SSDs.

Still runs like butter.

That’s true, but it also wasn’t fair to be a Wayland detractor then.

Nvidia needed to do stuff to make that combination viable, and their delay in doing so wasn’t anyone’s fault but Nvidia’s

Well then do it! There’s probably VM images around with a working installation

I think having separate standard APIs for screenshots, screen capture, and video capture that aren’t married to one implementation makes sense.

I partially agree about the focus on containers/sandboxes. Yes, it makes sense to criticize that something designed for a different use case results in different trade-offs. But on the other hand, are the use cases really that different? We’re talking about standalone desktop apps, they need some common building blocks no matter if they’re containerized or not, right?

Otherwise I don’t know enough about the standards to comment there, you’re probably right!

If you bring the two parts of your comment together and dial back the assumptions of bad faith, you’ll get a consistent picture:

Wayland is a blank slate replacement for how to do window management on Linux. At some point it’ll become the standard for software that’s new or maintained. Unmaintained software that doesn’t talk to the internet and is therefore safe to run even with security holes will continue to be supported via XWayland. The giant scope and API surface is part of the reason why it’s deprecated. Maintainers are expected to target the new way to do things going forward, because there are people able and willing to maintain that support (many of those people former X11 maintainers who are looking forward to stop having to deal with that legacy behemoth)

That’s the state of things I wanted to express. Not my opinion, no agenda, just how I understand the situation.

And that’ll shake out in the time it takes for X11 to go away. I get what you’re saying, although I don’t share your opinion about portals from a user perspective: I’m just happy that Firefox finally uses the Plasma file picker.