Yo whatup

  • 1 Post
  • 23 Comments
Joined 11 months ago
cake
Cake day: September 28th, 2023

help-circle










  • Traister101@lemmy.todaytoTechnology@lemmy.worldNeo-Nazis Are All-In on AI
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    2 months ago

    We do know we created them. The AI people are currently freaking out about does a single thing, predict text. You can think of LLMs like a hyper advanced auto correct. The main thing that’s exciting is these produce text that looks as if a human wrote it. That’s all. They don’t have any memory, or any persistence whatsoever. That’s why we have to feed it a bunch of the previous text (context) in a “conversation” in order for it to work as convincingly as it does. It cannot and does not remember what you say



  • Yup, libraries should usually let the consumer chose what to do with an error, not crash the program without a choice in the matter. The only real exception is performance critical low level code such as the core of a graphics or audio driver. Though in those cases crashing also often isn’t an option, you just power through and hope things aren’t too screwed up.




  • I’d probably say it depends but I’m no Rust expert and I have no direct experience with C (though quite familiar with C++).

    Basically I’d expect writing C to be easy, but not safe. IE you can quickly and easily write C that compiles but has runtime issues. Rust for the most part will catch everything but logic issues during/before compilation meaning once the program runs you’ll have very high confidence in it’s runtime behavior leading to time spent “fighting the compiler” instead of figuring out wtf is going wrong at runtime.


  • Yes Rust is harder to write than C, that’s basically by design as it’s due to the statically guaranteed memory safety. That’s pretty magical. C doesn’t have that and neither does C++ even with smart pointers and such. Rusts unsafe keyword is poorly named, what it actually does is tell the compiler that you the programmer guarantee Rusts rules are upheld within the unsafe block.

    For example

    Access or modify a mutable static variable

    That is a global, that’s incredibly hard to impossible to statically prove it’s safely done, so you have to do it in an unsafe block. So you violating Rusts rules within an unsafe block is actually using the unsafe block wrong. That’s not what it’s for




  • Yeah no… After enough scrolling through your history I see you being a bit of a nutter. That’s not people trying to “silence you” it’s you being crazy and people giving you werid looks. You are at best a troll at worst huffing trumps farts to a worrying extent.

    Can’t say anything about the comments removed by moderators but seeing what isn’t removed makes me suspect they were probably quite vile to get removed while those others stayed.