Even if it works despite being AI slop that’s been developed in a mere 4 days (?) and somehow has all these contributors, I’m not sure I agree with the idea.

It’s cool that they went with Rust for it, but I would have much preferred if all that effort went towards improving GIMP and existing open formats.

If it works then I guess it’s the same end result at the end of the day, but it would suck if GIMP doesn’t end up being the one to put a nail on Photoshop’s coffin after all these years of serious development by humans.

Edit: I already see the kneejerk dislikes coming, I’m just interested in starting a conversation about the idea of it, I also dislike the fact that it’s AI slop as I already implied. I’d appreciate joining the conversation instead of dislike bombing with no argument.

  • starsoaked_lily@lemmy.ml
    link
    fedilink
    English
    arrow-up
    32
    arrow-down
    1
    ·
    1 month ago

    even the people over on hacker news concede that they are unusably buggy so… i think vibe coded slop is vibe coded slop - use gimp

  • Joe Bidet@lemmy.ml
    link
    fedilink
    arrow-up
    32
    arrow-down
    2
    ·
    1 month ago

    Arguing such thing is “open source” is misleading as 1/ contributors can hardly call themselves “authors” of this code 2/ nobody can demonstrate that the plagiarizing engine they used did not plagiarize proprietary source code or source code published under an incompatible license.

    as in “you cannot claim a room is clean if you have never been in it, haven’t built it, and cannot even know what’s in it”

    • MalReynolds@slrpnk.net
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 month ago

      Not to mention the hoard of software patents Adobe will unleash their horde of lawyers with if this becomes anything more than a bad joke. Although that would make for an interesting precedent.

    • 3abas@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      2
      ·
      1 month ago

      Adobe would have to prove the model that generated this was trained on its stolen code. And Adobe’s code contains zero Rust while the Craft suite is 100% rust, so it’s certainly not simply regurgitating Adobe’s code.

      If you learn from others by studying their code, is the organic artisanal code you create also necessarily stolen?

      Let Adobe prove AI is trained on their codebase. Fuck Adobe, and fuck the copywrite system.

  • Random Dent@lemmy.ml
    link
    fedilink
    English
    arrow-up
    29
    arrow-down
    2
    ·
    1 month ago

    On the one hand, I am opposed to AI slop.

    But on the other hand, I am greatly in favour of anything that makes life even slightly more difficult for Adobe.

    This is a tricky one.

    • thingsiplay@lemmy.ml
      link
      fedilink
      arrow-up
      7
      arrow-down
      3
      ·
      1 month ago

      On the one hand, I am opposed to AI slop.

      Me too. But what is Ai slop? To me it is either fully vibe coded, or partially. Either way the user of the Ai ends up not knowing exactly what is going on. That is slop. But if its very carefully used, analyzed, understood, iterated and tested, like a human code would be, then I cannot call it slop. But it doesn’t take away the problems using Ai in the first place. There are inherent ethical issues, and questions if the licensing and copyright will become an issue one day.

      In short, not every usage of Ai is slop. But every usage of Ai has ethical unanswered questions.

  • okwhateverdude@lemmy.world
    link
    fedilink
    English
    arrow-up
    24
    arrow-down
    1
    ·
    1 month ago

    Not really a clean room implementation. Source has been leaked. Plus GIMP and other FOSS tools that implement the same functionality are in the training data. Very likely this “clean room” implementation is just laundering code.

    • ferret@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      1
      ·
      1 month ago

      God I wish one of these megacorps would bite on suing one of these projects, if only so there is precedent of punishment for AI code-theft. The fact that they won’t touch them for fear of damaging their golden goose means it’s de-facto fair use.

      • grue@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        1 month ago

        I have to admit, “AI copyright laundering Mexican standoff” isn’t an angle I had considered.

        • pory@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 month ago

          Honestly it’s one of the few scenarios I did consider at the start. On the one hand, your megacorps like Disney (for example) absolutely want to replace human artists with slopbots. On the other hand, Disney does not want Joe Rando to be able to type “make me a Spiderman comic” into the slopbot.

    • Voroxpete@sh.itjust.works
      link
      fedilink
      arrow-up
      5
      ·
      1 month ago

      In this case the clean is probably “We told Claude to write it and we don’t care if Claude has a bunch of leaked Adobe source code in it’s training data.”

  • communism@lemmy.ml
    link
    fedilink
    arrow-up
    18
    ·
    1 month ago

    If the authors used the same method to improve GIMP, they’d be introducing a bunch of slop code to GIMP. This code is not going to be of GIMP quality.

    I also doubt this will hold a candle to GIMP for the aforementioned reasons. It might appeal to a small audience, but I do not expect it to dethrone GIMP any time soon.

  • Lettuce eat lettuce@lemmy.mlM
    link
    fedilink
    arrow-up
    16
    arrow-down
    2
    ·
    1 month ago

    From their own documentation:

    opening and re-saving a document renders the same for 307 of the 309 files in the psd-tools test set and 169 of 170 in our mixed ag-psd/psd-tools set

    Just what I want in my editing software, the assurance that my saved files will mostly render properly when reopened in the same program…

    This is exactly what will sink any attempts to do similar things, it’s not the broad functionality of the software, it’s all the billions of edge cases.

    The LLMs will be able to get all the general requirements mostly right, and that’s where it will stop. The subtle errors and bugs will pile up steadily as the codebase grows too large and complex for even frontier models to accurately summarize, and the people who vibed it to begin with don’t actually understand what is happening, so they can’t troubleshoot effectively.

    Automated bug reports will pile up, agents will be dispatched in greater numbers, leading to cost issues and further complicating and compounding the errors in a bloated and convoluted codebase. The leads of the project will get burned out and abandon the project, leaving a giant, rotting, husk behind. Software that was forever, “almost working properly.”

    • Dnb@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 month ago

      They aren’t saying that opening and saving their own files corrupts. They are saying their psd saving is 99% the same as adobe’s.

      • Lettuce eat lettuce@lemmy.mlM
        link
        fedilink
        arrow-up
        2
        ·
        1 month ago

        I know they are talking about PSDs, they listed it in their test suite. I read it as the test working for all but a few tools, but I guess they could just be talking about coverage.

        Either way, it still does and will suffer from all the same issues I listed in my comment.

  • pineapple@lemmy.ml
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    1
    ·
    1 month ago

    I will be extremely surprised if this comes anywhere near gimp. AI is not at the stage were is can create amazing software all by itself. It will likely be buggy and/or feature incomplete.

  • thingsiplay@lemmy.ml
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    1 month ago

    It would be okay, if it wasn’t Ai. I think using LLMs cannot be guaranteed to be a clean room implementation.

  • ZkhqrD5o@lemmy.world
    link
    fedilink
    arrow-up
    11
    ·
    1 month ago

    To be honest, I think these things will be abandoned very quickly. Therefore I don’t think that there will be any competition to the “flagship” FOSS projects anytime soon. However, in the proprietary world, it’s money above all else, and I think that we’re going to see the quality of proprietary software degrade very quickly. Because why pay engineers to do work if you can have a text generator that does it cheaper and gets there 80% of the way, and then just release it.

  • Artemis_Mystique@lemmy.ml
    link
    fedilink
    arrow-up
    10
    ·
    1 month ago

    As I have said many times: license washing works both ways, this is the end of proprietary software as we know it, no more would I have a need to install a sketchy driver inside a windows VM just to use some crap USB microscope

  • SpatchyIsOnline@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    1 month ago

    I don’t know how anything developed by an LLM can be considered a cleanroom reimplementation. The AI has almost certainly seen the source code of the project it’s reimplementing, even of it’s proprietary because the developers of said software are likely using the AI too

  • /home/pineapplelover@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    7
    ·
    1 month ago

    Oh yeah my coworker was walking about this. Someone spent about $2k in tokens recreating the Adobe suite on windows, macos, and linux. Crazy what AI is able to do nowadays.

    I don’t think I will use it but I feel like in a year or two, software written like this will be everywhere