vrighter

except that it can, and regularly does, regurgitate copyrighted works verbatim.

because they don't understand why it's printing money

so the creator of gif himself was deliberately transgressive?

i love the dougdoug ones for that

but in games, triple buffering is the norm

I had lots of cars the size of burgers though, when I was a little child

that's just how the code is rendered. There's still all the usual constructs

except that they literally say it is.

!

because we can

doesn't have to be a cube

new features are fine. But first and foremost, is not breaking existing apps, or committing to porting them yourself. So if desktop apps need to do xyz, then wayland needs to support doing xyz. period. No 'but that's insecure', no 'but why would you want to do that' (for setting a window icon or positioning the window ffs). Support existing applications. I'm not saying it should support x protocols. But it should offer replacement features for existing apps to be ported to. And it needs to be wayland. Because it's already the case that certain functionality is implemented for gnome, or kde, with incompatible apis, to fill in the void left by wayland itself. If I want an app to work as I want it, consistently, everywhere? X, with all its warts, is my only choice.

As an example, the accessibility protocols. They're good to have. Except they're opt-in. So incompatible with existing apps. Some apps need to restrict access. They could declare that and make use of additional functionality. But no, choose a default that break everything instead.

The argument that apps just need to be ported also assumes the app is still maintained. Are you willing to do the work yourself if not? Probably not. You're just the one looking down on people like me for wanting functionality in existing apps to be "not literally impossible to implement"