I wonder if there are different use cases. You sound like you’re using an LLM in a similar way to me. I think about the problem and solution, describe what I need implemented, provide references in the context (“the endpoint should be structured like this one…”) and then evaluate the output.
It sounds like other folks are more throwing an LLM at the problem to see what it comes up with. More akin to how I delegate a problem to one of my human engineers/architects. I understand, conceptually, why they might be doing that but I know that I stopped trying that because it didn’t produce quality. I wonder if the newer models are better at handling that ambiguity better.
I agree with you, but my gut tells me that a lot of people don’t know what a good outcome should/could look like and are accepting whatever it delivers.
I just sync down everything from my wife/kids’ Google Drive/Dropbox/whatever nightly to my NAS. Usability of a cloud solution, but with on-prem backup.
Surely there's no way that's true. The logical conclusion of that would be that every random ToS is a law that everyone must abide by, regardless of whether or not they've agreed to it.
By definition, it is exactly a law. It's known as business law. The ToS is a business contract which you must agree to if you wish to use the service. Violating terms of service is literally a breach of contract.
How can you breach a contract if you are not a party to a contract? OpenCode is not using any Anthropic services, they are just publishing some source code that seems (obligatory IANAL) to be protected speech under the First Amendment [0], if this legal argument is happening in American jurisdiction.
Interesting point. I've been looking into a similar issue recently, and for example LinkedIn won a lawsuit against the analytics company hiQ because they violated their ToS for scraping their website. And I think they also never technically had a direct contract they'd breach.
Yeah good point. I think if the scraping code is written specifically for a site / system that prohibits scraping through it's ToS, the company has an edge for a lawsuit. It's a bit of a gray area I think. It depends how much of a threat you form to the company you're scraping, and how big the company is.
> What is sure is that a lot of capacity is been built and that capacity won't disappear.
They really are subsidizing what will be an incredibly healthy used server equipment market in a year or two. Can’t wait. My homelab is going to be due for an upgrade.
It sounds like other folks are more throwing an LLM at the problem to see what it comes up with. More akin to how I delegate a problem to one of my human engineers/architects. I understand, conceptually, why they might be doing that but I know that I stopped trying that because it didn’t produce quality. I wonder if the newer models are better at handling that ambiguity better.
reply