3 ms·
> This is not a good outcome for people who want an independent OSS ecosystem. I understand why this is not ideal for Elastic-the-company, but is it a bad outc
by CharlesW 6y ago
> This is not a good outcome for people who want an independent OSS ecosystem.
I understand why this is not ideal for Elastic-the-company, but is it a bad outcome in the longer term?
As someone who is happy open source exists but uses mostly proprietary software, this seems like a natural and expected response to an open source project adopting a more restrictive license.
- mrkurt 6y agoI think we're all better off if small and midsized OSS companies thrive. Amazon is not inventing and open sourcing DBs. For the last 15 years, we've relied on independent companies to advance the state of the art for _all of us_. Amazon has no reason to build a compelling database and release it to the community. When the giant tech companies do open source they're work, it's usually an attempt to improve their existing market at the expensive of another company: Kubernetes, OpenDistro, Firecracker, and most of the CNCF projects follow this pattern. A fork is a natural response to an OSS project license change. But when the company that _forces_ the license change also creates the fork, it's gross.
- CharlesW 6y agoGreat points and a helpful perspective, thank you.