• charokol@lemmy.worldEnglish
    37·
    8 hours ago

    I know nothing about rust but I assume borrow checker is some integral part of it that this guy somehow has never heard of?

    • calcopiritus@lemmy.world
      55·
      8 hours ago

      Yes. Someone that knows just a little more of rust than you do would know what the borrow checker is.

      It’s the core feature of rust.

      Like talking about java and not knowing what “inheritance” is.

      EDIT: just so you understand how vibecoded that project is.

      The dude says he vibecoded “some of it” because some rust features make it a hard language for him. The one feature he’s talking about is the borrow checker.

      It’s like saying “man, sure is hot today”. Someone says “yeah, this summer sure is hot” and the dude replied “yeah, summerians lived in a hot place too”.

    • Limitless_screaming@kbin.earth
      17·
      7 hours ago

      Very integral. When someone says they’re “struggling with Rust”, it’s thanks to the borrow checker.

      Rust’s whole shtick is the way it manages memory, which is the rules enforced by the borrow checker.

      Basically:

      When you want to store values in variables in any programming language, the memory should be allocated when you need it and freed as soon as you don’t anymore.

      Traditionally there are two ways this is done:

      1. You manage it completely yourself, which is “unsafe” as you can forget to free memory you no longer need. This is called leaking memory. Or “reference” the location of something you freed previously, thereby attempting to read data you may not have permission to read (the OS will usually prevent that and kill the program), or reading and using a value you didn’t expect, causing undefined behavior and fun to deal with bugs.

      2. The language, sometimes using a process which runs alongside your main program, manages memory. Which adds lots of overhead.

      Rust has it’s own way of doing this: It adds some rules on how you can pass around references and ownership and these rules are affected by whether you can or can’t edit the referenced data. All just so the compiler knows the lifetime of the vars that hold that data and when it can free it (before the program is even compiled, so no overhead when the program is running). Not following the strict rules prevents your program from being compiled into an executable.

      The compiler gives very helpful info, tips, and pointers™ though, Rust is also know for this.

  • pewpew@feddit.it
    18·
    8 hours ago

    Uses rust because it’s memory safe but it is vibe coded and the developer doesn’t know what a borrow checker is.

    Just use a high level language at this point

  • one_old_coder@piefed.socialEnglish
    1042·
    12 hours ago

    the language restriction of rust

    Rust has no restriction. The restriction is in his brain high on AI.

    make sure to star the github repo so that I can create more projects like these.

    That’s not how any of this works, he’s crazy.

  • floofloof@lemmy.ca
    27·
    10 hours ago

    This is the new normal, it seems. My developer colleagues are bragging about how long it has been since they wrote a line of code.

    • four@lemmy.zipEnglish
      5·
      5 hours ago

      Sometimes I lament how long it has been since I wrote a single line of code, because I had to do reviews, testing, management, etc.

      I guess some of us like the aspect of coding (as in writing code), while others only like the results (be it the product or the pay)

      • floofloof@lemmy.ca
        4·
        5 hours ago

        Yes, I have always enjoyed trying to create elegant architecture and code, more than I get satisfaction from the end result. I’ve always found it frustrating how many colleagues were prepared to throw together any old junk as long as the right thing came out in the end. On the positive side, maybe the AI does raise the quality of what some of them contribute.

    • criss_cross@lemmy.world
      6·
      6 hours ago

      My favorite is seeking feedback on reviews on stuff we own and people not responding and being like “I’m sorry I had Claude create 500+ PRs I can’t possibly respond to everything”

      You don’t think there’s a problem with that!?!?

    • uuj8za@piefed.socialEnglish
      151·
      9 hours ago

      Same.

      They always say that so proudly too. “It was all the AI bros!”

      me staring at the mountain of shit they just plopped in front of me

      Yes, I can tell.

      • forkDestroyer@infosec.pubEnglish
        61·
        8 hours ago

        Devs on my team are straight up saying in the sprint retros that the code is slop and needs to be modified after AI makes the suggestion. Our repo is being flooded with garbage that works out of the gate but costs so much extra to troubleshoot when it fails.

  • Solemarc@lemmy.world
    812·
    12 hours ago

    Those are such weird responses, is that user an agent?

    Instead of “yes I vibecoded X because of Y” we get the classic respond like you’re trying to hit the word limit on your essay.

    • FiniteBanjo@programming.dev
      412·
      11 hours ago

      Sloppers spend so much time talking with their shitbots that they tend to use similar vocabularies and prose. Some of them do have AI write up their responses, too. Some of them even integrate Grok directly into their keyboard.

    • Ephera@lemmy.ml
      23·
      11 hours ago

      I also like how they claim it’s completely different to KRunner and then, save for OCR and whatever “circle to search” is, these are all features in KRunner.

  • CaptDust@sh.itjust.works
    541·
    12 hours ago

    “It’s not entirely vibecoded but…” Mmmmhmm. Wish people could just be transparent with themselves and their audiences.