[–] 0 points 11 months ago (11 children)

I don't understand why this never type was introduced at all. Instead functions not returning, shouldn't Rust enforce returning from function and instead use a None in place of never type? Otherwise how will the "Unwinding" of program flow implemented?

  • source
  • parent
  • context
  • [–] 0 points 11 months ago (1 child)

    so people who are dating aren’t dating?
    sounds like some “going steady” bs that i’ll have no part of.
    “oh we’re dating but we’re not dating dating”
    people are so afraid of using their vocabulary they just add new definitions to words….
    just like George Orwell warned against

  • source
  • parent
  • context
  • [–] 14 points 11 months ago

    OP used the original title. Author of article has since updated it. If you read the comments on the article itself you can see evidence of this.

    Let’s be a little more attentive and not jump to conclusions. ;)

  • source
  • parent
  • context
  • [–] -2 points 11 months ago (1 child)

    Downvoted for clickbait headline editing, which was actually:

    The (successful) end of the kernel Rust experiment

    Let's be a little less breathless and a little more considered. please.

  • source
  • [–] 13 points 11 months ago

    Concluded might have been a better term for them to use. It means effectively the same thing but implies the natural expected end rather than potentially some other reason for ending (such as Linus pitching a fit and yanking it early).

    It's good to see it's doing well enough to be considered a success despite some of the interpersonal drama around it.

  • source
  • parent
  • context
  • [–] 21 points 11 months ago (2 children)

    I knew it would be this. There was no other way, as it would be too sudden. Still little bit clickbaity, but I let it pass, because this is not a YouTube video or blog post for clicks and advertisement money.

  • source
  • [–] 4 points 11 months ago* (last edited 11 months ago)

    The CEO of Socket is this guy. I'm not sure that someone with those credentials would be heading a company engaged in what basically amounts to racketeering. Though, I suppose he might be unaware it's happening. The company has many investors, any of who would benefit from creating an environment that supports the company's existence without the awareness of any of the employees. But it's clear this isn't some scam operation run by desperate people out of India, which was my first thought from reading your comment. There are reputable people with their reputations at stake. It would be a Theranos-level scandal if what you say was actually determined to be occurring. So, on the one hand, there are reputations at stake, and, on the other hand, Silicon Valley is not incapable of committing fraud.

  • source
  • parent
  • context
  • [–] 6 points 11 months ago* (1 child)

    I didn't. And I was specifically referring to the published "analysis".

    How do we know the supposedly malicious content (which hasn't provably affected a single person) a security company finds, didn't originate from that same company?

    • Crates NO ONE uses or ever used.
    • "with over 7,000 all-time downloads" immediately mentioned to make it sound like the above is not the case.
    • Our "AI" found a malicious base64 (wow, very fancy)!
    • Muh supply chain!
    • bla bla China bla bla

    It all sounds like a joke, and a lazily written one at that (Edit for fairness: the ctor part was a nice touch tbf).

    And this is not limited to this analysis, or this company, or the Rust ecosystem. The era of CVE logos and all that theater can become rather tiring, and AI slop took the silliness to a whole other level. Or as our friend Daniel puts it, it's a "Death by a thousand slops".

  • source
  • parent
  • context
  • [–] 13 points 11 months ago (2 children)

    If you use Linux, this is a good reminder to spend a bit of time learning AppArmor / SELinux. rustc / cargo and processes spawned by them shouldn't have access to your entire $HOME.

  • source
  • view more: ‹ prev next ›