radiant_bloom

joined 1 year ago
[–] [email protected] 1 points 4 months ago (1 children)

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

[–] [email protected] 6 points 4 months ago (1 children)

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

[–] [email protected] 5 points 4 months ago

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

[–] [email protected] 13 points 4 months ago (10 children)

I just want more things on Peertube.

[–] [email protected] 1 points 4 months ago

Georgism ❤️

[–] [email protected] 1 points 4 months ago

It’s crazy that there even are “categories” for discrimination that are disallowed. Why not disallow all discrimination, hm ?

[–] [email protected] 1 points 5 months ago (2 children)

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.

[–] [email protected] 3 points 5 months ago (1 children)

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.

[–] [email protected] 1 points 5 months ago (2 children)

Did that with a mouse yesterday ! But I expect she was likely eaten by one of the many neighborhood cats in the following hours.

[–] [email protected] 36 points 5 months ago (1 children)

The sadder thing is that Chinese social credit hasn’t actually even been implemented, and doesn’t seem like it’s going to. There are only limited local experiments, most of which are allegedly largely irrelevant.

Whereas there are multiple credit score companies currently tracking literally everyone who has a bank account.

[–] [email protected] 0 points 5 months ago (14 children)

The improvement here is switching from interpreted to compiled. It could have been C, Zig, Odin, or even C++ (but thank Satan it isn’t C++)

I’m not sure I understand why people like Rust over C, although I don’t have that much experience in enterprise coding. I’m generally distrustful of languages without a standardized specification, and I don’t really like that Rust has been added to the Linux Kernel. Torvalds giving in to public opinion isn’t something I thought I’d live to see…

I get the segmentation fault thing, but to be blunt, that sounds like a skill issue more than an actual computer science problem.

Maybe if things were less rushed and quality control was regarded more highly, we wouldn’t have such insanities as an email client (or an anything client) written in JavaScript in the first place.

Rust is likely going to suffer the same problem as JS, where people indirectly include 6,000 crates and end up with 30 critical CVEs in their email client that they can’t even fix because the affected crate was abandoned 5 years ago…

[–] [email protected] 1 points 5 months ago (2 children)

I would say yes. The only time you don’t is when I already agree with you, but that’s because I (hopefully) already know the good argument.

I don’t believe in “common sense”, that’s just the biases someone already has. Some of them correct, some of them not, all unchecked therefore all invalid as a basis for anything.

view more: next ›