• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: July 12th, 2023

help-circle
  • I don’t currently have a computer powerful enough to host a top tier LLM like chatgpt4. If I can’t even run it, I sure as shit could never continue to train it with new data. I often use chatgpt with my phone and the thought of doing either one is ridiculous.
    There are ways to make money on open source outside of the open source item itself. Redhat has done just that with Linux.
    An LLM is just software. No matter what algorithm, tool, or fairy magic was used to amalgamate the data it consumed, they all sucked in open source code and just like any other software that includes open source software, it should be subject to the licensing on the open source software, which pretty much means they should be open source themselves. Companies that want to make money off of AI trained on public data can make their money on the value they add, just like redhat.
    The biggest issue I see right now is how to deal with AIs tendency to output data untransformed. Trademark and all those types of licenses are negated as long as the idea within is transformed, but it is really hard to argue transformation when the stupid thing is pooping out word for word quotes, but acting as if it is “new” and transformed.











  • Yes. I mean often enough that I wouldn’t call it rare.

    You are a front-end js/ts devel, aren’t you? That makes sense. I can understand why you would have such a skewed view of programming. When everything you write is disposable and might be scrapped every 2 - 3 years, comments would seem like nonsense and a waste of time.

    But that is definitely not everyone’s experience. More than half the code I have written has had a minimum 15 year life expectancy. Comments are essential to remember what I was doing in whatever random language I had to use at a given point. I might not comment on “x++;” but I sure as shit will on “x += (xDelta * yDelta + 31) / 32;” Actually, that’s not true, if the logic is complex enough for the rest of the code chunk, I might just comment on “x++;” to make it clear what x is in this case and why it needs to unconditionally be incremented here. Even if the reason seems ridiculously obvious right now. Because that shit might not be obvious at all in 10 years.