dralley

27 ms·

541.
by dralley 2y ago
> The Department of Energy spent this week trying to contain the fallout from its DOGE-directed firing and rehiring of a brace of nuclear safety officials by painting them as non-critical staff who “held primarily administrative and cler
542.
by dralley 2y ago
The market deserves some blame here.
543.
by dralley 2y ago
Also https://lore.kernel.org/rust-for-linux/1f52fa44062e9395d54ed...
544.
by dralley 2y ago
Marcan quitting wasn't a compromise, the resignation of a maintainer would never be used that way. Dude was just burnt out. I don't blame him at all, hopefully some time away from the situation does him some good.
545.
by dralley 2y ago
There was no reason to ever think otherwise. The experiment wouldn't have happened if he didn't want to try it and give it a certain amount of backing. He's been pretty vocal about his motivations. https://www.yo
546.
by dralley 2y ago
Allowing C++ would lead to endless debate over exactly which subset of C++ is allowed in the kernel, and would be a pain in the ass to police. The point of Rust is that it offers enough facilities to the programmer that you can right near-b
547.
by dralley 2y ago
Linus appears to agree https://lore.kernel.org/rust-for-linux/1f52fa44062e9395d54ed...
548.
by dralley 2y ago
It was indeed brought up.
549.
by dralley 2y ago
>It would be less problematic if used for different purposes or layers, like frontend and backend. Good news! At the present moment, Rust is only being used for drivers. Who knows if that will change eventually, but it's already t
550.
by dralley 2y ago
Probably relevant: https://www.wsj.com/business/media/x-hinted-at-possible-deal... >A lawyer at advertising conglomerate Interpublic Group fielded a phone call in December from a lawyer at X. >The message wa
551.
by dralley 2y ago
Both Linus and Greg KH were actively supportive of the project and remain so. Several of the R4L developers were long-term linux devs long before the project started (e.g. David Arlie). There are lots of current maintainers who aren't
552.
by dralley 2y ago
>amid a growing ultraconservative embrace of Russian values Just like the USSR-praising leftists that came before them, these ultraconservatives have a fantasy notion of "Russian values" in their heads that bears no resemblance
553.
by dralley 2y ago
>Presumably, this is an investment in replacing code written in C. There's no way around abstraction or overhead in such a venture. Nobody is proposing replacing code right now. Maybe that will happen eventually, but it's of
554.
by dralley 2y ago
Userspace, yes.
555.
by dralley 2y ago
Linus doesn't like ADA much, and the talent pool is FAR smaller and also FAR older on average. The compelling reason to use Rust over other languages is precisely that it hit escape velocity where others failed to do so, and it did th
556.
by dralley 2y ago
That's hardly a novel framing. It's even brought up in the very email thread (not by Greg KH) that we're discussing.
557.
by dralley 2y ago
The opposing view is that drivers written in Rust using effectively foolproof APIs require far less maintainer effort to review. Yes, it might be annoying for Christoph to have to document & explain the precise semantics of his APIs an
558.
by dralley 2y ago
Plenty of Linux maintainers are either fully or partially on board with using Rust in drivers. Don't overindex on the opinions of two or three of them that are vocally opposed / skeptical. Christian is a special case because his
559.
by dralley 2y ago
ABI is irrelevant. Only external APIs/ABIs are frozen, kernel-internal APIs have always been allowed to change from release to release. And Rust is only used for kernel-internal code like drivers. There's no stable driver API fo
560.
by dralley 2y ago
There are multiple kernels written in Rust already. Writing another one wouldn't be interesting. The point of R4L is that people want to write drivers for Linux in Rust. The corporate sponsors that are involved also are interested in
561.
by dralley 2y ago
It's only relevant to the current debate in the sense that that event was the trigger for Wedson (the first and OG R4L project contributor) to quit, which was only a few months ago, so it's a fresh wound marinating in the backgrou
562.
by dralley 2y ago
Clarity was apparently provided privately. However, I have to say that a public statement would have been better. I can only imagine how demoralizing it is for the R4L contributors to watch their work being trashed in public and the leade
563.
by dralley 2y ago
Like 75% of those lines of code are in drivers or architecture-specific code (code that only runs for x86 or ARM or SPARC or POWER etc.) The amount of kernel code actually executing on any given machine at any given point in time is more li
564.
by dralley 2y ago
Most of it already was, but normies don't go looking for public expenditure databases, so they assume it doesn't exist. Then DOGE comes along and pretends they're doing something new.
565.
by dralley 2y ago
"Life of the mother" restrictions don't work. Doctors operating under threat of severe legal liability will second-guess the woman to death. Many such cases, in Texas and elsewhere.
566.
by dralley 2y ago
Elon is partly responsible for the conditions he is exploiting. He was an active participant in pushing to get all sorts of "special" treatment.
567.
by dralley 2y ago
How did Marko Elez get re-hired.
568.
by dralley 2y ago
Shit headline. This is referring to lifetime costs, and the article mentions: >This increase is in part due to the extension of the service life of the aircraft from 2077 in 2018 to 2088 in 2023. Many of the ongoing operational costs ha
569.
by dralley 2y ago
At least they're funding a lot of useful open source development with that money pile.
570.
by dralley 2y ago
All of your points can be summed up as "Congress refuses to do their job". Breaking all the laws to bypass the government does not "actually address and fix systematic problems with the US government", that is an absurd

More ›