3 ms·

there's no "they", there's only us. AWS paying to use it means we are paying to use it. Between that and a truly Apache 2.0 project, I think it's a no-brainer f

by ssgao 8y ago

there's no "they", there's only us. AWS paying to use it means we are paying to use it. Between that and a truly Apache 2.0 project, I think it's a no-brainer for everyone.

sagichmal 8y ago
Why shouldn't you pay to use it, then? More generally: why should AWS get to leverage its near-monopolistic position in the SaaS market to perform essentially hostile takeovers of the software projects it packages and runs? Simply because they have the resources to do it?
- e1ven 8y ago
  I'm very glad that they've done this. The code was open, and the company decided to close it for the new versions, so it forks. Forks are common when people don't like the corporate direction of an OSS project - It's a strength, not a weakness. Openoffice/Libreoffice, Hudson/Jenkins etc. Imagine if Linus said that the next version of Linux would be paid-only. Within 15 minutes there'd be a new librelinux repo that people could contribute to instead. Someone was going to make a new fork anyway - This is Amazon putting their money where their mouth is to fund and support that new fork.
  - dhd415 8y ago
    To be clear, no Elasticsearch code or features that were OSS were closed. As new Elasticsearch features are developed, some of them are now released as OSS and others are released with a commercial license.
  - anth_anm 8y ago
    Okay, are you glad that Amazon now owns Elasticsearch?
- therealx 8y ago
  If ES didn't do the weird license change thing, we wouldn't be here. Either Amazon wouldn't have used it, or they'd be paying. Including non-com features in the default install was not a good way to play things. Would you feel the same if AWS built a drop in/api compatible system from scratch?