[Gigachad]

This is the frustrating part of being a linux user. Absolutely massive time periods before changes. Literally no work is done until it eventually changes, everything breaks, and people scramble to fix it. Which more desktop oriented distros would just drop xorg next year and we actually get the last remaining apps updated.

[Arnavion]

It has nothing to do with being a "Linux user" and everything to do with being an LTS OS user. Not being bowled over by rewrite-the-world changes is why rolling release distros exist.

And before anyone says it, no "rolling release" doesn't mean "unstable".

[Gigachad]

I'm on Fedora which is pretty up to date and I just have random issues all the time. Currently I can't get xbox controllers to pair. It works on windows, it worked on fedora when I tried a few months ago, absolutely can't get it working now. When I switch audio outputs, they don't work until I kill pipewire a random number of times and then they work.

And these are just the random breakages, not the missing features like fractional scaling and HDR. Obviously these problems don't affect everyone, but they affect me and despite a decade of linux experience, I can't find solutions.

[Volundr]

Counterpoint: I run Arch Linux on all my machines and I can't remember the last time something broke that wasn't ZFS, and I opted into that one, it's explicitly unsupported. I switch between a Bluetooth headset and my speakers/webcam multiple times a day and it just works (I'm also using pipewire, not pulse).

[rektide]

There's the guy on my team who is steaming mad at Sindre Sorhus for making all his npm packages ESM only. https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3...

The time line is a little more compressed. I'm somewhat sympathetic. But my heavens, that using the language's official module system is a pain & difficult makes me think we needed to switch harder earlier.

(Also Node simply lacked the courage to try to do what many before them had done, & make cjs/ESM intercompatible: worked great in @std-things/esm but node let themselves get steered into prissily rejecting an obviously fine path for absurd technical minutia).

We gasp & moan the whole time old soggy gross bandaids are being ripped off. We direly need to call shots & make it happen. We need the will.

[toyg]

& as a shorthand to "and" makes you look like a child, discounting everything you say. Just sayin'.

[rektide]

Is there anything else anywhere that points to this strong bias you have? I have seen one other person bother to comment, in a slightly more sly negative way, counting how many '&'s I used.

I obviously dont seem to share the sensitivity, it seems natural to me, and I'm not sure where these feelings & reactions come from. I feel like there should be some substantiation or discussion, something available, if & for and is so unsettling to folks.

[toyg]

It hinders readability just to save you two keystrokes, you are effectively telling people "fuck you, I don't care about the effort you'll have to make to parse my gibberish". Plus, of course, I'm sure you know almost no-one else uses it like that, so you come off as begging for attention. Both are very childish approaches, when trying to communicate with peers.

[npteljes]

This is the frustrating part of being a user, of any system. Change is risk, and why take risk? In case of Wayland, I see no upsides as a user. At most, it works as well as xorg did, which is to say, in the background, doing its job, for me to not worry about it.