Comment by buster
1 day ago
Well.. Old discussion but I actually think it's the better way (sorry. MIT, you are more free then anything). Either contribute back or stay away from open source work that others did for you.
1 day ago
Well.. Old discussion but I actually think it's the better way (sorry. MIT, you are more free then anything). Either contribute back or stay away from open source work that others did for you.
Can you even copyright LLM output? Even the readme points out humans didn't make any of the code.
In this case you just can't spin it any other way than it being a derivative work of Blender. And this is great.
My understanding is that the LLM stripped away the non-UI code from Blender. The majority of the code is ported directly from GPL'd code from the Blender code base.
Most software is not GPL. When comparing this to alternatives like EGUI and GPUI for building a new app, this cannot be considered, while the others can.
GPL makes sense for applications like Blender. For a general purpose library, it's a dealbreaker.
It depends on what you're building. If your app is free software, a GPL library is no problem at all. (and your own code can even stay MIT or Apache.)
It "cannot be considered" only for proprietary apps.
This is not the spirit of open source.