I don't think you understand the qualifier. I meant in the tradition of liberal free markets that have unlocked human potential on the global scale. I'm saying no it's actually good that you don't have to ask the local government when you want to do something. If American style free markets didn't gain traction we'd still be doing subsistence farming.
The thing is, since we recognized that such a tradition led to the unfettered destruction of the natural environment which we depend upon to survive, we have decided that local governments should be responsible for preserving said environment by regulating the destructive actions performed by the liberal free market. Not doing so will even destroy our ability to perform subsistence farming in the long run.
So far all I hear is complaining about electricity prices. No one actually cares about the "environment". They are just mad that the KW/h is up 3 cents.
It's controlled by a guy who spends all day retweeting white supremacists and lying about his companies. Why should anyone who isn't a white supremacist use it?
It seems to be a common view on HN that licenses and conditional access to websites should be ignored (i.e. WRT ad-blockers), but also that licenses on Open-Source Software repositories should be respected (i.e. WRT LLM training). I believe that holding these contradictory views is common, but the conflict would need to be resolved to come to a conclusion on how to proceed with LLM training.
Replication is not the same as reproduction; I can replicate an API without violating someone's license or copyright (which I would by reproducing their work).
Developers are permitted to learn from open source code with restrictive copyrights, and apply those lessons to developing other software which does not comply with the copyright of their 'example'.
As an aside, I do believe that LLM trainers are ignoring and violating many licenses, but open-source software is not a clear example of a violation.
Depends on how you define "learn": usually, a company wanting to rebuild and publish something under a different license prohibits their developers from having ever looked at original code, to avoid the risk of copying over exact snippets out of their memory accidentally.
Copyright protects only arbitrarily non-trivial parts of the original being reproduced, but that means that you have to be careful with learning from copyrighted material. Programming books will have direct clauses allowing snippet reuse, but not for teaching purposes.
> Sure, but developers are permitted to learn from open source code with restrictive copyrights, and apply those lessons to developing other software which does not comply with the copyright of their 'example'.
This was a different argument. And there is no contradiction to separate LLMs and people.
> As an aside, I do believe that LLM trainers are ignoring and violating many licenses, but open-source software is not a clear example of a violation.
You seem to be conflating copyright with access rights. Two very different things. Regardless of your feelings on either, there is no contradiction in holding different views on them.
Well no, it’s about legally gating the ability to copy so the original author doesn’t have to compete in the same market to sell his own book with every other bloke with a printing press and a copy of the book. Everything else is an addendum.
Don’t confuse the social justification with the actual purpose of copyright law just because it’s written into the US Constitution that way. America didn’t invent copyright law.
Where and when? In cases where LLM coding assistants reproduce copyleft code in someone's work assignment? The responsibility in those would be on the user, not on AI.
Are you doing a full search of every GPL licensed repository every time you use an LLM to ensure that it isn't giving you GPL licensed code? That doesn't seem reasonable
That's because licenses are an abstract complexity tacked on to a simple material reality in order "to promote the progress of science and the useful arts".
Just like many cultural rules, they keep growing in complexity until they reach a phase change where they become ignored because they have become too complicated.
OSS licenses haven't grown in complexity all that much in the past forty or so years. They're being ignored more now because it's become easier to ignore them, not because it's become harder to abide by them.
This has basically been my experience since Sonnet 3.5. I've been working on a personal project on and off with various models and things since then and the biggest difference between then and now is that it will do larger chunks of work than it did before, but the quality of the code is not particularly better, I still have to do a lot of cleanup and it still goes off the rails pretty frequently. I have to do fewer individual prompts, but the time spent reviewing the code takes longer because I also have to mentally process and fix larger chunks of code too
Is it a better user experience now? Yes. Has it boosted my productivity on this project? Absolutely.
But it still needs a ton of hand holding for anything complicated and I still deal with tons of "OK, this bug is fixed now!" followed by manually confirming a bug still exists.
At least 4000 years ago, but that's just the earliest we have evidence for
https://en.wikipedia.org/wiki/Code_of_Ur-Nammu
reply