I think the “controversy” is just tribalism. I’ve never once witnessed a case of any of the negative adjectives thrown at the Rust community. They’ve always taken exceedingly fair and good-faith approaches to discussing any critique of the language.
Their snark is reserved for the weird “anti-woke” crowd that hates Rust for some reason.
I just use nushell’s builtins instead of wrangling with IFS and bash idiosyncrasies. It’s been years since I’ve corrupted data by parsing text wrong.
But even if someone doesn’t want that: apart from using it in legacy scripts, grep is just a strictly less useful ripgrep these days, no?
I really like rolling release. So much better to deal with updates one-by-one than in a giant batch every half year or so.
As said: installing the LTS kernel also works, I think.
And you wouldn’t use Arch for servers, you want something stable (as in “rarely changing”) there.
I agree that it’s be useful, and I think you can just install e.g. the LTS kernel next to the regular one.
But even without , the arch way isn’t insane either: when something kernel-related breaks, boot with a live system on USB and fix it.
Case in point: I dimensioned the EFI partition too small, so at some point, me using the zen kernel (which comes with a backup kernel image) messed things up and I couldn’t boot a half-written kernel.
then I
/ and /boot partitions manually into /mnt/root/ and /mnt/root/boot/dev and /proc into /mnt/root/{dev,proc}/mnt/root (resulting in an environment using /dev and /proc from the live system and the rest from my system),It’s not crazy, it doesn’t take long, you just need to know how the system works. Upside is that nothing ever breaks permanently, everything is fixable (except hardware failure)
The reason there’s no version in the filename is simply that Arch just doesn’t keep old kernels around.
The vmlinuz-linux just gets replaced whenever you update the linux package and the old one is deleted immediately.
Cool parasitic fungus too!
It would only be propaganda if it wasn’t organic. But people just really actually like it and like to talk about it.
If you don’t like that, may I suggest not engaging with the content and just scrolling past it?
Oh yeah I have to deal with software that noticeably changes multiple times per decade! Spoooooky!
Is that some meme? My system has been rock solid for years.
Thanks, this is a much more nuanced take than what I’m used to.
Regarding thinlinc: They seem to be on it: https://community.thinlinc.com/t/wayland-tigervnc-and-thinlinc-the-future-of-remote-desktops-in-linux/1755.
Regarding fragmented support: is that true? Why would some CAD software not work everywhere when most other software does? Does the thing really need some specific niche Wayland protocol that’s only implemented on one DE for the time being? And if yes, will that protocol really be the first relevant one to not be implemented across the board? I feel like you’re conjuring to a problem that doesn’t necessarily exist. Do you have an actual concrete example that goes beyond “the subwindow placement for this multi-window program is a bit wonky without impeding usability in the slightest”?
Maybe you didn’t do it right. Everything Wayland I ever complained about is fixed now.
I fell like if you had put this list into a Wayland protocol extension request, then put a link to that request into KDE’s showstoppers list, this would have been fixed long long ago.
OK, let’s see if I remember well:
OSS is obsolete.
ALSA is a basic primitive way to do play audio streams integrated into the kernel.
PA is an abstraction on top of ALSA that helps with network stuff, per-application volume control, …
JACK is an alternative to ALSA/PA for low latency professional use cases: you can plumb it yourself, connect inputs/outputs, …
PW is an efficient implementation of both PA and JACK, which is better than the original PA in latency.
Which isn’t true, at least one of them has Wayland support already, the rest is following suit.
Yeah. In the first months, there were clipboard issues. Until 2 years or so ago for me, screen sharing wasn’t perfect.
I searched for or filed issues whenever I could, and there’s not a trace of a problem left.
I wonder if these people just complain on social media and give up immediately without informing anyone relevant and then feign surprise when shit’s not magically fixed later.
You’re so right:
Pretty good for mostly volunteers, hampered by recalcitrant project leads that actively sabotage any progress and consider “told you so” appropriate.
If anyone cared enough, they could have made that list 17 years ago, and pushed through a set of protocol extensions that allow talon to work.
Why did nobody do that?
It’s crazy to me that people complain now. It’s far too late for complaints.
I don’t get what you mean. Isn’t the list just a status quo and not how things are supposed to be forever? What’s “hilarious” about somebody painstakingly going through all the features and checking how close they are?
Like I wouldn’t put it past GNOME to give up on interoperability at the slightest inconvenience, but I don’t see that here?
I like the heading styles! The tildes are unusual but the reasoning is sound!