• 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
      ·
      13 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.