• BigDanishGuy@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    2 hours ago

    So… Clean build? But with the added bonus of risking some AI destroying the code? Cool, just what the world needed: a worse way of doing something you been doing effectively for a couple of decades

  • Scipitie@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    0
    ·
    1 day ago

    Anyone downvoting this has:

    • Not looked at the repo
    • Not looked at the community
    • Has a hate boner for the two letters L and M if combined in a certain way.
    • Missed out
    • ggtdbz@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      0
      ·
      11 hours ago

      I remember GPT2TC, LLMs were a very interesting niche little proof of concept software area for a few years before <incoherent exasperated gesticulations>

    • lanigerous@feddit.uk
      link
      fedilink
      English
      arrow-up
      0
      ·
      23 hours ago

      The AI disclaimer is brilliant:

      Ironically, aside from the obvious use of LLMs for the actuall project, everything was written by hand. I wanted to use this as a learning opportunity about git filters, so everything you see is my fault.

    • palordrolap@fedia.io
      link
      fedilink
      arrow-up
      0
      ·
      1 day ago

      Well, I’m not going to downvote, but something in my brain is screaming “lossy compression!” and so you might say I’m at least wary.

      • Mikina@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        12 hours ago

        It is a tremendously stupid idea, which is why I found it funny (also, it’s one of those things where name came first and inspired the rest).

        But, to take it seriously for a moment (and I’m not trying to defend it, not a fan of LLMs as most of the people here), is it necessarily lossy? I mean, you basically have to include the 5Gb large model for it to work, and you just move the data from the file to hoping the summary can trigger a correct combination of parameters.

        I didn’t run any larger tests, and I assume that if you managed to keep the API/function names and behavior, the summary would be actually longer than the actual implementation in most cases anyway, so it’s probably not even a compression (especially if you include the model).

        It’s just a food for thought, it’s definitely a bad idea to do something like this, to the point where I’m pretty sure you could get millions from investors if you made a startup working on something like this (and that one already exists), but I do honestly wonder if the fact that you kind of have the data in the model would still count as lossy.

    • Fiery@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      0
      ·
      1 day ago

      Sneak peak for people too lazy to read the very short readme:

      Does it actually work? About just as much as any reasonable person would expect

    • ☭可爱小猫☭@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      10 hours ago

      I have read an article about their own engineer has forgotten how to write native application for their own fucking operating system. I wonder even a LLM can make good win32 app.