Yeah. The plucky rebels pretty much won against the evil empire, but the forces of darkness weren't completely beaten. They regrouped and then repurposed the rebels tools against them. The might of venture capital, big tech, SaaS, hyperscalers and AI was too much. The rebels weren't decisively beaten so much as eventually eroded out of any real significance.
MIT and other non copy left licenses were a mistake. In the 2000s and 2010s people were so concerned with usage and GitHub stars of their OSS that they just gave everything away to corporations and now don't have the right to complain anymore.
Can you point at projects that got abused that way? I see plenty of things that got written by corps or by conglomerates, many of which landed with Apache. And I see lots of copyleft software that pulls whole systems with it.
What’s something that was released as MIT but, had it been GPL2, would have seeded a community?
Mostly it's not stuff that would've had a community if it was GPL - it's stuff that would've had a community either way, then Amazon took it and made it proprietary and took the community too.
I don't think it's quite correct to say that Amazon made these projects proprietary. They're perfectly willing to contribute upstream - the issue is they stole the margins from the companies that were trying to offer hosted versions of their products.
IMO this is unfortunate but must be allowed if we want to have truly open licenses.
What do you mean? GPL licenses aren't truly free! They limit the right of corporations to abuse users! That can't be right! Better to use another license on the off chance you'll win the VC lottery.
I generally agree with fighting corporate abuse, though IMO, GPLv3's anti-tivoization clause is kind of misguided. It may stop locked-down hardware makers from using your software, but it doesn't stop the hardware from being locked-down in the first place.
We have evidence that any hardware maker that would open up their hardware will do it already (see: reMarkable, Ubiquiti offering SSH root access). If you try to fight that battle by holding software from them, you only lose them as a contributor as they make their own, which is worse for everyone.
Like, what? Solaris/SunOS, DEC Ultrix/Tru64, AIX, HP-UX, Xenix, etc., all with big bad monopolist AT&T's UNIX as their grandpappy. UNIX was corporate to the hilt.
Corporate, sure, but painting DEC, (old) HP, and Sun with the same brush as AT&T, IBM, and Microsoft just because they sold proprietary, but generally well-documented and reliable hardware and software at whatever prices the market would bear seems unfair.
Kubernetes is the last thing I wanted to see recreated for agents. It’s like Multics of cloud, now for agents. Complexity for the sake of it, powered by your favourite YAML slop bowl.
Huh. The idea is interesting, but I don't understand the decision of keeping it chat-like: it looks like the mix of the worst parts of Google Docs and Slack, I struggle to see how this will help people track decisions.
This can be improved though - I think that simply a separate collaborative doc and a chat linked to that doc would work way better.
Based on comments below the solution is to make the API public and publish the architecture design, along with the binaries.
This way the company can avoid spending too much money on open sourcing the code, and the community can just rewrite the server while keeping the original binaries running.
This is a very myopic and unnecessary cynical sentiment. It's not about you - agents just need to run without your computer being on all the time. Coding is a background task that needs to run unattended now.
This is absolutely not true. I run dozens of Opus agents all day and they need so much constant attention and babysitting (lest everything turn to sh*t) that I would not qualify it anywhere close to “background”. And I’m sure as hell not wrangling these things from my *phone*.
I predict that ntsync will eventually evolve into full blown ntoskrnl.ko and there would be virtually no overhead on calling Windows API. You can almost call it a Linux Subsystem for Windows.