191–200 of 673 posts
License - what AWS did is "legal", most commercial software is built on top of OSS.
Decency - what AWS did was mean. They should at least acknowledge the author.
Worst possible outcome of this thread: the community will become scared of big corporations stealing their hard work - this will stifle OSS creativity.
There are some replies in this thread that misunderstood the content of Tim Nolet's twitter post. (Probably because the short headline has pitchfork raising overtones.) - He's not complaining that Amazon forked his code with Apache license. He admits he also uses other open source with permissive licenses - He just thought it would be nice/courteous/polite/etc if Amazon acknowledge/recognized/credited/mentioned/thank…
If you read further down the Twitter thread you’ll see others point out that AWS actually DID acknowledge him in the release and thus his original rant isn’t accurate. He acknowledges that later in the thread. Of course the, now inaccurate, headline Tweet remains the thing getting attention.
Is the author calling them out fair. Yes.
Also fair, me assuming everybody defending AWS here is a terrible person.
Earlier quoted context omitted.
> Open source software is more than a license and code. It is a community and the digital public square. Unfortunately, there's absolutely nothing about the OSS community that actually instills this mantra in people. I like to think that I also see OSS as a community and digital public square, but there's no universality to that philosophy. > Either we as a community hold ourselves and others within our community to…
> OSS is a great thing that has tremendously benefited the industry I'm beginning to question this. The proliferation and commoditization of F/OSS is what made SaaS business thrive, and made it so that integration and polish is the only avenue left to make a buck, leading to our paltry attention economy, oligopoly, and platform lock-in by network effects. This after decades of personal computing striving to liberate…
Congrats, your work was good enough to turn into a commercial project by a major top 3 cloud provider. That would make me feel like I would stand a little taller! You basically created a new AWS service, as v1, that's pretty cool to add to a CV ;) Just be patient, and make sure you figure out the colour of your Lambo now.
This is sarcasm, right? Right?
Situations like this are precisely why the industry pushes so hard for APL and BSD/MIT, and against A/L/GPL: because you do the work and they make the money.
The OP posted "Show HN: Headless Recorder" https://news.ycombinator.com/item?id=24577642 > 22 days ago. Amazon forked and released it as a service. They are efficient.
Wrong post. It was over 2 years ago. https://news.ycombinator.com/item?id=17760536
I'm extremely disappointed to see how many comments on here focus on the very narrow legal questions and amount to: "Your license didn't say they couldn't." Open source software is more than a license and code. It is a community and the digital public square. And the Tragedy of the Commons is just as applicable to our public square as it is to William Forster Lloyd's common land. Either we as a community hold ourselv…
If it were the case that AWS broke some unspoken social convention that is hard to legally enforce, I'd be more sympathetic. But it feels more like the author made a choice to license their software using Apache 2 over other licenses.
Individual developers spend their free time developing a solution without making as much as a cent, while giant corporations are making billions on it.
How did that become a thing?
Earlier quoted context omitted.
If you read further down the Twitter thread you’ll see others point out that AWS actually DID acknowledge him in the release and thus his original rant isn’t accurate. He acknowledges that later in the thread. Of course the, now inaccurate, headline Tweet remains the thing getting attention.
Are people really expecting the devs at AWS to give a "thank you" to every third party developer out there who's code they use? This is just ridiculous. When does this become an obligation? Is there an unwritten rule of how large/successful a team has to be before they need to give thank's like this?
There are some replies in this thread that misunderstood the content of Tim Nolet's twitter post. (Probably because the short headline has pitchfork raising overtones.) - He's not complaining that Amazon forked his code with Apache license. He admits he also uses other open source with permissive licenses - He just thought it would be nice/courteous/polite/etc if Amazon acknowledge/recognized/credited/mentioned/thank…