• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: August 28th, 2023

help-circle
  • 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.


  • radiant_bloom@lemm.eetoMemes@lemmy.mlAmericans be like
    link
    fedilink
    arrow-up
    40
    arrow-down
    3
    ·
    7 months ago

    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.


  • 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…









  • We don’t know. However, no one cares about your personal photos ; no one will ever attempt to hack you specifically unless you’re a high value target (in which case, stop hosting your photos anywhere immediately)

    The only thing that could get your photos is if an undiscovered backdoor is exploited by someone doing some sort of a mass attack. As far as I know, they’re pretty rare, because people with the means to do them generally have a specific set of people they care about (which you are unlikely to be a part of).


  • That is a real problem.

    I hope we can find a solution for that, but as of now living without producing e-waste is literally impossible, so I don’t really bother my mind with the exact quantity.

    If I keep buying smart watches at this rate, in 30 years I will have produced around a single smartphone’s worth of e-waste from them, and that’s if literally none of it gets recycled.

    ( My phone (iPhone 13 mini) is approximately 6x the size of my watch (Watch series 4) ; and I’ve had that one for 6 years. I’m only replacing it if it doesn’t get the next watchOS, which I won’t know until WWDC, so I made a pessimistic guess that it won’t for the calculation. )