• 0 Posts
  • 482 Comments
Joined 2 years ago
cake
Cake day: September 2nd, 2023

help-circle

  • calcopiritus@lemmy.worldtoTechnology@lemmy.zipLLMs Will Always Hallucinate
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    3
    ·
    2 days ago

    No it is not. It is the same as saying you can’t have coal energy production without production of CO2. At most, you can capture that CO2 and do something with it instead of releasing to the atmosphere.

    You can have energy production without CO2. Like solar or wind, but that is not coal energy production. It’s something else. In order to remove CO2 from coal energy production, we had to switch to different technologies.

    In the same way, if you want to not have hallucinations, you should move away from LLMs.







  • Maybe some people don’t delete the fork after their PR is done.

    In my case, I found another explanation.

    Sometimes, a random person comes and forks one of my repos. I check their profile, and it’s a techbro student with hundreds of forked repos without any commits. With their bio referencing AI or some shit.

    I’m pretty sure these people fork a lot of repos just to pad their CV or something. Make it look like you have a lot of repos. Because when you go to someone’s profile, it is not clear that a repo is a fork instead of their own creation.





  • The problem with that is that reviewing takes time. Valuable maintainer time.

    Curl faced this issue. Hundreds of AI slop “security vulnerabilities” were submitted to curl. Since they are security vulnerabilities, they can’t just ignore them, they had to read every one of them, only to find out they weren’t real. Wasting a bunch of time.

    Most of the slop was basically people typing into chatgpt “find me a security vulnerability of a project that has a bounty for finding one” and just copy-pasting whatever it said in a bug report.

    With simple MRs at least you can just ignore the AI ones an priorize the human ones if you don’t have enough time. But that will just lead to AI slop not being marked as such in order to skip the low-prio AI queue.






  • The problem of this is always the same. Contractors. Is your janitor holding the wage of your CEO down? Easy fix, you are the CEO. Fire the janitor and hire a cleaning company. Since the employees of the cleaning company are not your employees, their wages are no longer relevant.

    At some point, the CEO can just have its own company of 1 employee (himself) which owns 100% of the stakes of the real company, and he can also be CEO of the real company. The real company would just pay massive amounts to the CEO company for “IP” or “consulting”.

    This policy can be implemented voluntarily by companies, but I don’t think a government can make a law to implement this policy without obvious loopholes.



  • There are use cases. Like containers where the pointer to the object itself is the key (for example a set). But they are niche and should be implemented by the standard library anyway. One of the things I hate most about Java is .equals() on strings. 99.999% of times you compare strings, you want to compare the contents, yet there is a reserved operator to do the wrong comparison.