radiant_bloom

u/radiant_bloom@lemm.ee
0 posts · 86 comments

Recent posts

No posts.

Recent comments

on ... · c/fediverse · 5 pts · 2y

I would give so much money to Patreons if I wasn’t broke myself šŸ˜…

on ... · c/fediverse · 11 pts · 2y

Honestly, I’m murdering the productivity of every channel I watch anyways with uBlock origin and sponsorBlock, so I don’t think it’d be much worse

on *Permanently Deleted* · c/europe · 5 pts · 2y

By the same logic if the planet explodes there’s going to be problems. Just because you can invent a scenario in which it’s a bad idea doesn’t mean that scenario exists.

on ... · c/fediverse · 64 pts · 2y

I just want more things on Peertube.

on *Permanently Deleted* · c/europe · 8 pts · 2y

Call me crazy but I think all immigration should always be legal šŸ¤·šŸ»ā€ā™€ļø

Honestly you should ! Unless you want to do crazy stuff you actually don’t need to learn the entire documentation.

I was able to setup full disk encryption with encrypted boot loader pretty easily, there are great tutorials out there. I’m going to figure out Secure Boot next.

The nice thing is that once you’ve managed to do something, it’s in your config forever. My main problem with Arch was the absence of rollbacks, and having to remember all the stuff you do when installing it that you inevitably forget before the next time your system breaks and needs a reinstall. There’s none of that with Nix, and it’s awesome.

Now I’m not a shill but I did switch from Arch to Nix (because my Bluetooth was irremediably broken on Arch, and no one responded to any of my posts) and it’s honestly a lot less complicated than the documentation suggests šŸ˜†

Why do you want sophisticated code ? That word seems out of place from the other two to me.

Rust doesn’t introduce the same problems as C, but it sure does introduce a lot of other problems in making code overly complicated. Lifetimes and async are both leaky abstractions (and don’t even work as advertised, as rust-cve recently demonstrated), macros can hide control flow…

C is unsafe, sure, but also doesn’t pretend to be safe. C is also stupid simple, and that’s a good thing : you can’t just slap ArcMutexes around, because by the time you know how to code them yourself you also know why you shouldn’t do that.

I hope Rust can reach a point where its safety model can be formally proven, and we have a formal specification and a stable ABI so we don’t have to hard-compile every crate into the binary.

But I personally expect something with some of Rust’s ideas, but cleaned up, to do that instead. Actually, I wouldn’t be surprised if C itself ends up absorbing some of Rust’s core ideas in an upcoming standard.