[–] 2 points 1 week ago*

The main outcome from this is that it forces the companies to not out-source the development/maintenance/support to AI. If they do, they are literally no different from just self-hosting this and asking your own LLM for help, which is going to be cheaper.

As usual, automation actually reduces the rate of profit in the long run.

This is probably the most realistic goal of the movement.

  • source
  • parent
  • context
  • [–] 6 points 1 week ago*

    But in all seriousness, they’re still unmaintaible slop

    They are definitely more user-friendly and community-maintainable than the closed-source originals.

    Originals are either binaries you can't modify, or completely black-box inaccessible software someone else runs which you only interact with.

    Having some source code which does almost the same thing, even if it's buggy, is much better than having nothing at all.

    Of course AI has its own issues and the resulting software is pretty bad. It is a great starting point to be improved tho.

  • source
  • parent
  • context
  • [–] 52 points 1 week ago

    Probably the same way Unity feels about their game engine being associated with awful low budget shovelware games. The game engine was popular with low budget games because you can use the engine for free… But you have to display the “Made with Unity” splash screen for a few seconds as your game boots up. And notably, you can pay a licensing fee to remove that splash screen requirement. Basically the drug dealer special: Get the newbie game devs familiar with the engine for free, then charge the publishers to use the engine that their employees all already know.

    The issue (which Unity didn’t initially foresee when they wrote their licensing terms) is that all of the shovelware games used Unity for free, and all of them had the big “Made with Unity” splash. So Unity very quickly became associated with super low effort shovelware games.

  • source
  • parent
  • context
  • [–] 1 point 1 week ago (4 children)

    if you've worked with a proprietary codebase at all, you can not be let even close to a reimplementation or it's legally not clean-room

    That is incorrect though. The idea behind clean room is in the name: if you take even the same idea, write a spec, and SOMEONE ELSE does a different implementation, you're fine. The someone else here is AI. And no, AI output is not patentable nor IP infringement, unless there is a case I missed something. Adobe is extremely litigious, so they haven't made a move yet. They have no case.

  • source
  • parent
  • context
  • [–] 10 points 1 week ago* (1 child)

    *Whisper: self hosted LLMs

    Dario: We gotta pace the frontier 😆

    But in all seriousness, they're still unmaintaible slop. But who knows maybe in X years they get better. I see a better use case in software cracking libre sourcing

  • source
  • parent
  • context
  • [–] 43 points 1 week ago (1 child)

    So instead of fixing the balance with your human Rust code, you instead associate the language as slop because people choose it for their slop projects since it's much safer and fast?

    If anything, the slop projects working efficiently and not crashing every 5 minutes is the best proof you can have that Rust is uniquely great at what it offers, every language should aim to protect the program from its weakest link programmer which is AI in this case

  • source
  • parent
  • context
  • view more: ‹ prev next ›