radiant_bloom

If it integrates properly with tv that will be one thing better than Netflix at least…

I would give so much money to Patreons if I wasn’t broke myself 😅

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

Take money from the poor while fixing nothing. Business as usual 🤷🏻‍♀️

I just want more things on Peertube.

Georgism ❤️

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 😆

The config file thing works better for NixOS, but the même is still very funny !

I admit to not knowing how running an open source project goes, but wanting more contributors seems like the wrong metric compared to better contributors.

I understand the pitfalls of C are not limited to segmentation faults, but I suspect it would be more productive to fix C by including some of Rust’s better ideas than to throw it away, as seems to be the current trend.

I don’t think Rust is wholly bad, to be clear, but it seems over-engineered to me, and the fact its useful new features don’t even completely work (see rust-cve) isn’t very encouraging.

I would recommend listening to Jonathan Blow’s opinion on Rust, which I tend to agree with. I personally think I’m just going to stick with C until Rust either becomes the standard, or I retire and let the next generation worry about that.

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.