Your point about it being a culture issue is spot on. Many maintainers who are established in the kernel have made it clear they'd rather keep the status quo and the comfort of stagnation rather than bring a new technology forward to improve the security of their systems.
If it wasn't Rust, but some other language with similar benefits, the same people would've thrown their hands in the air and complained that they're being forced to rewrite everything or some other hyperbole.
Because it's a FOSS project, for some reason it's acceptable for maintainers to be entitled arseholes who abuse anyone they personally have a vendetta against.
In any other workplace, this behaviour wouldn't be called "nontechnical concerns" it would be called workplace bullying. And as much as Linus wants to say he's working on his anger issues, he is personally one of the contributors who has set this culture of aggression and politicking as much as any other.
This isn't Rust's fault lmao, this is distro maintainers trying to fuck with dependencies on software which has been proven to be a horrible way of managing software distribution for years.
When it's a problem with other languages, we don't pin the blame on them. However, because Linux and its developer community is being dragged by its heels to accept ANYTHING more modern than C99 and mailing lists, the typical suspects are using any opportunity to slow progress.
The same shit has happened/is happening with Wayland. The same shit will happen when the next new technology offers a way for Linux to improve itself. A few jackasses who haven't had to learn anything new for a lifetime are gonna always be upset that new Devs might nip at their heels.
Because it's Rust it's now "rust bad" but Debian and other distros have been fucky with dependency management for YEARS. That's why we're moving to flatpak and other containerised apps!
Once again, the wider Linux dev community is trying to openly kneecap the first attempt in decades to bring Linux and its ecosystem up to a vaguely modern standard.
TLDR Debian and the traditional Linux package management system is antiquated and insecure, but somehow this is the fault of one of the many programming languages that is designed around the sensible expectations of being able to manage your own dependencies.
All you need nowadays for a decent Unix-like is compatibility with a handful of Linux softwares and a web browser. Hell, if you could get WINE working on your kernel you could maybe support as many Windows apps/games as Linux for free.
The big issue, as I see it, is performant drivers for a wide range of hardware. That doesn't come easy, but I wonder if that can be addressed in a way I'm too inexperienced to know.
But projects like Redox are a genuine threat to the hegemony of Linux - if memory safety isn't given the true recognition it deserves, projects like Redox serve to be the same disrupting force as Linux once was for UNIX.
If anything, the constant coddling of a few aging individuals within the kernel and the protection of their comforts is why Linux has been so slow to adopt technologies and paradigms that developers are begging for.
Linus complains of dev burnout starving the kernel of contributors, but the processes and technologies driving kernel development are antiquated, and the very suggestion of change is either discarded or makes you the target of a public shaming by Linus himself.
It was never about replacing C with a new language for the sake of novelty, it was about solving the large majority of security vulnerabilities that are inherent in memory-unsafe languages.
If Rust were to implode tomorrow, some other memory-safe language would come along and become equally annoying to developers who think they're the first and only person to suggest just checking the code really hard for memory issues before merge.
The video attached is a perfect example of the kind of "I'm not prepared to learn anything new so everyone else is wrong" attitude that is eating away at Linux like a cancer.
If memory safety isn't adopted into the kernel, and C fanaticism discarded, Linux will face the same fate as the kernels it once replaced. Does the Linux foundation want to drag its heels and stuff millions into AI ventures whilst sysadmins quietly shift to new kernels that offer memory safety, or does it want to be part of that future?
I have no context to the thread that caused this struggle session but as a vegan and someone who knows for a fact people will take that shit out of context anyway I know that most vegans will either not have pets, or if they do don't go as far as to malnourish it.
Most vegans interested in a "vegan cat food" are purely seeing a bunch of tinned/pouch food that claims to be nutritionally complete. I know that for some here the assumption is that vegans are trying to force feed Mr fluffles a carrot and kale soup.
As for whether that food is nutritionally complete depends on the animal, the brand, the testing, and the regulations. Turns out there's a lot less rigor in ensuring foods are safe for animal consumption compared to humans!
The takeaway overall, imho, is that this is one of those times where having an "/R/all" frontpage makes for a great opportunity for a pile on, followed by mod overreach, and then a weird ass ToS change that's more to spite a few people than to do any good.
Lmao all this over meat eaters getting mad at vegan cat food? I'm genuinely impressed that redditors are managing to turn Lemmy into a caricature of the godawful website they left.
This is the limitation with policy made by people who just think "science" is when you quote an opinion with an article in a journal.
Decades of climate denialism, anti-veganism, and "race science" is perfectly acceptable under these rules because you could simply post studies funded by Exxon, meat and dairy lobbyists, and right-wing think-tanks which support their conclusion.
"Science should prevail" nerds could do well to consider that perhaps we have other means of identifying malicious behaviour. Any kind of checkbook exercise or algorithm that can pluck truth out of the air won't work; the scientific method was never intended to declare X or Y as permanent facts the way we use it online.
True, though for most game/graphics developers you're never interfacing directly with the graphics API, you'll let your chosen engine/library do the heavy lifting.
It does have the downsides of increasing the barrier to entry for custom/bespoke engines but those edge cases seem to be covered well by DXVK.
Your point about it being a culture issue is spot on. Many maintainers who are established in the kernel have made it clear they'd rather keep the status quo and the comfort of stagnation rather than bring a new technology forward to improve the security of their systems.
If it wasn't Rust, but some other language with similar benefits, the same people would've thrown their hands in the air and complained that they're being forced to rewrite everything or some other hyperbole.
Because it's a FOSS project, for some reason it's acceptable for maintainers to be entitled arseholes who abuse anyone they personally have a vendetta against.
In any other workplace, this behaviour wouldn't be called "nontechnical concerns" it would be called workplace bullying. And as much as Linus wants to say he's working on his anger issues, he is personally one of the contributors who has set this culture of aggression and politicking as much as any other.