Yes and no. It would solve some problems, but because it has no (non-hacky) graphics acceleration, most DEs wouldn’t use it anyway. The biggest benefit would be from not having to use a DE in some circumstances where it’s currently required.
Each monitor should have its own framebuffer device rather than only one app controlling all monitors at any time and needing each app to implement its own multi-monitor support. I know fbdev is an inefficient, un-accelerated wrapper of the DRI, but it’s so easy to use!
Want to draw something on a particular monitor? Write to its framebuffer file. Want to run multiple apps on multiple screens without needing your DE to launch everything? Give each app write access to a single fbdev. Want multi-seat support without needing multiple GPUs? Same thing.
Right now, each GPU only gets 1 fbdev and it has the resolution of the smallest monitor plugged into that GPU. Its contents are then mirrored to every monitor, even though they all have their own framebuffers on a hardware level.
I asked my MAGA coworker whether he thought Trump broke the law in the hush money case, and his response was “she should have kept her trap shut”.
“Shut up about eggs”
- Trump’s retweet
Trump knows that his supporters are going to turn on him eventually, which is why he’s working so hard to set up an infrastructure that can crush opposition without due process. He’s also testing the waters about ignoring court orders.
If the supreme court lets him use the AEA then that means the president can use war-time statutes without Congress needing to declare a war, which means that he’ll be able to use a different statute to deploy the military on US territory. At that point, US democracy is officially over.
I’m not sure it’s possible to blame Trump rather than his voters when he literally promised to make most of these changes. It might be more effective to say that Trump was misled by Musk.
We’re not assuming, we’re speculating.
She’s Linux-adjacent :P
Freya Holmér is great.
Are trans women ok?
Perl should say: You are old and a nerd or you use Debian
I’d argue that most mainstream FOSS is extremely strong. Something like 80% of servers and 60% of smartphones run Linux. Up until recently, Cloudflare was using Nginx for their entire CDN. The thing they replaced it with is technically also FOSS. Probably most computers in the world are using OpenSSL or GNUTLS.
I think the real “weakness” of FOSS is that they don’t have the money or the desire to schmooze corporate decision makers. They also don’t have sexy GUIs, but anyone could contribute that if they wanted.
I didn’t include the social media “brigading” portion because Linus already addressed that in a different sub-thread.
I don’t know if there’s any precedence for this, but I could see a court asking to see the git commit log if things went that far.
I always advocate for FOSS solutions at my work, but most of the time I get shut down with some variation of “We prefer $MSP’s solution because it gives us someone else to blame if shit hits the fan”. I hate that sentiment, but I appreciate the honesty.
My job title is “Linux System Administrator”. I’d quit if they tried to make me drop Linux.
The boiled down summary is:
Christoph rejects the patch because he doesn’t want to maintain it
Christoph says no and that he “will do everything [he] can do to stop [Rust support from being added to the DMA subsystem]”
By saying that Hector is the problem, he’s implicitly saying that Christoph is not the problem. By saying that the current process works–the very same process that just prevented R4L from submitting patches to the kernel, he’s implicitly endorsing Christoph’s actions.
You’re probably right from a legal perspective, but the difference between “donation” and “salary” is pretty murky in this context.
Take this case, it all started over a bit of code. The subsystem maintainer refuses to take it. But it does not require any changes to existing code. It just has to be merged. Linus can take it directly. If he does that, the Rust folks can start to use it. The sub-system maintainer will lose in the end. At some point, the battle will be lost by those trying to block Rust. It all depends on Linus. We will see.
Linus hasn’t been merging the necessary code, by virtue of supporting a maintainer who was very obviously trying to sabotage R4L; if Linus was going to stand up for R4L, this would have been the time.
Nice