![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
I fucking hate GPU companies for always removing SR-IOV from their consumer cards
I fucking hate GPU companies for always removing SR-IOV from their consumer cards
And RCS on top of not being available in a lot of places, is a closed standard, no matter how Google tries to spin it.
I’m glad Meta seems to be keeping most of the junk they have on Insta/FB away from WhatsApp*
^*so ^far
0% fixing the multitude of crippling crashes and bugs that plague the software making it unusable for daily computing.
You say this in the comments of a blogpost where they are precisely doing that
Read also: Naomi Wu and the Silence That Speaks Volumes by Jackie Singh
Full text of the post by Asahi Lina (@lina@vt.social):
I regretfully completely understand Wedson’s frustrations.
A subset of C kernel developers just seem determined to make the lives of the Rust maintainers as difficult as possible. They don’t see Rust as having value and would rather it just goes away.
When I tried to upstream the DRM abstractions last year, that all was blocked on basic support for the concept of a “Device” in Rust. Even just a stub wrapper for struct device would be enough.
That simple concept only recently finally got merged, over one year later.
When I wrote the DRM scheduler abstractions, I ran into many memory safety issues caused by bad design of the underlying C code. The lifetime requirements were undocumented and boiled down to “design your driver like amdgpu to make it work, or else”.
My driver is not like amdgpu, it fundamentally can’t work the same way. When I tried to upstream minor fixes to the C code to make the behavior more robust and the lifetime requirements sensible, the maintainer blocked it and said I should just do “what other drivers do”.
Even when I pointed out that other C drivers also triggered the same bugs because the API is just bad and unintuitive and there are many secret hidden lifetime requirements, he wouldn’t budge.
One C driver works, so Rust drivers must work the same way.
Making the Rust bindings safe would have required duplicating much of the functionality of the C code just to track things to uphold the lifetime requirements. It made no sense. It would have been easier to just rewrite the whole thing in Rust (I might end up doing that).
To this day, bugs in the DRM scheduler have been the only causes of kernel panics triggered via my Apple GPU driver in production.
The design of that component is just bad. But because I come from the Rust world, the maintainer didn’t want to listen to my suggestions.
If it takes a whole year to get a concept as simple as a trivial “device” wrapper upstreamed (not any device model functionality, literally just an object wrapping a struct device so we can pass it around) then how is Rust for Linux ever going to take off?
Rust works. I’m pretty sure I’m the only person ever to single handedly write a complex GPU kernel driver that has never had a memory safety kernel panic bug (itself) in production, running on thousands of users’ systems for 1.5 years now.
Because I wrote it in Rust.
But I get the feeling that some Linux kernel maintainers just don’t care about future code quality, or about stability or security any more. They just want to keep their C code and wish us Rust folks would go away. And that’s really sad… and isn’t helping make Linux better.
I’m sorry but I think that’s just the way Java Edition goes mate, lol.
You see a modpack that recommends 6GB allocated and you think “oh, I’m fine, I have 16”, next thing you know you’re almost going OOM.
I have recently upgraded to 32GB solely because of ‘All The Mods 9’
This looks super neat but I don’t really like the idea of sending my shell history to a third party, nor can I host my own server right now.
Wish it was peer-to-peer like Syncthing
They’ll switch from Chrome to Cryptocurrency flavored Chrome and think all is well in the world.
I really wish Mozilla would focus on these missing bits and bobs like WebUSB and this one you mentioned instead of whatever the fuck it is that they’re doing now
Damn, squeezing all of that down to 4gb is impressive!
Spyware because of a feature you don’t even need to use? Geez.
ClownStrike
A fitting rename after such a pathetic and catastrophic failure, that’s for sure.
Ah, so search a couple of domains and sit on their page for a while making random mouse movements and scrolls then? Got it.
Wow I have fully embodied the meme after reading this
Chinese OEMs love to do this for some reason, my phone says"ULTRA PREMIUM" right near the flash.
I already bought the device Xiaomi, you can stop advertising it to me now lol.
So. Fucking. True. oh my god.
I want to turn Bluetooth on in a script!
Linux? Two or three commands.
Powershell? Here, run this monster or download an application to do it for you and call that via the command line.
Last time I used Windows, the only way to suspend the machine was either poking some random ass .dll from System32 or downloading PsSuspend by Sysinternals ffs!
Well I really dislike updating my computer (and on this topic, Windows Update is inconvenient and slow as balls!) and finding some new BS from Microsoft on it.
One day it’s Copilot, which I could just use on the browser if I really wanted to, the next day it’ll be Recall, which just… no.
Know what I mean?
Widely considered?
Surprised to hear that, whenever someone posts him on Lemmy most of the comments act like he’s the best thing since sliced bread in video form
Okay, and now find a messaging app that supports RCS that isn’t Google or Samsung messages.
Being stuck to 2 apps, one of which is OEM exclusive sure defeats the point, now doesn’t it?