Elasticsearch became popular on back of being F/OSS. The "our code" Shay talks about is community's too: All the evangelizing through blog posts, talks; and the countless hours spent reporting bugs or even fixing them. If anyone thinks a community's contributions are any less than their own company's, then they don't get to claim to be torch-bearers of F/OSS (which Elastic is without realizing the irony).
Shay keeps claiming "our users" aren't affected, but who's he fooling? They say, AWS cornered them to adopting dual-license SSPL, what's to say they woudln't do an Oracle in the future (like Sun did with Java and continue to do with their DB offerings?). Slippery slope, sure, but it is indeed slippery for a company struggling to compete with competition and seeking predatory avenues as last ditch attempt to stay alive.
I believe, in all my naivety, that Elastic could have created an Elastic Foundation (like Joyent did with NodeJS, who btw didn't throw a hissy-fit at AWS for Lambda) and invited developers from all walks to shoulder the burden of the core software (which they themselves commoditized by F/OSSing it) so that they could focus on SaaS (like AWS).
I'd like to think, Elastic's real problem is they have hard time competing with AWS in terms of pricing for SaaS (of course, AWS owns infrastructure and so it is a tough battle-front), but if they were paying any attention, AWS Elasticsearch Service was very poor in 2015 and continued to remain so for a long time (it sucks less now), but Elastic's own service wasn't up to the mark, either. I think they misplaced their priorities (see GCP's flawless execution with k8s, managed-k8s, and Anthos) and were caught asleep at the wheel when they could have captured SaaS market away from AWS in those interim years (2015-19) by focusing solely on differentiated features and not on the core Elasticsearch software (which was libre and hence undifferentiated).
Of course, Shay and Elastic know better than I do and I am indeed a grumpy developer who's upset, but I want Elastic to give up their misleading messaging viz. 'doesn't affect / nothing changes for our users'. They're being hypocritical and not doing anyone any favours.
> And to be clear, this change most likely has zero effect on you, our users. And no effect on our customers that engage with us either in cloud or on premises.
No, Shay. It does affect the community, who are also the users of the software.
> We created Elasticsearch; we care about it more than anyone else. It is our life’s work. We will wake up every day and do more to move the technology forward and innovate on your behalf.
I see a lot of "We"s and "Our"s. And that's the problem with CLAs and stealing someone else's work. Companies can't tell anymore who's stealing from whom.
Shay keeps claiming "our users" aren't affected, but who's he fooling? They say, AWS cornered them to adopting dual-license SSPL, what's to say they woudln't do an Oracle in the future (like Sun did with Java and continue to do with their DB offerings?). Slippery slope, sure, but it is indeed slippery for a company struggling to compete with competition and seeking predatory avenues as last ditch attempt to stay alive.
I believe, in all my naivety, that Elastic could have created an Elastic Foundation (like Joyent did with NodeJS, who btw didn't throw a hissy-fit at AWS for Lambda) and invited developers from all walks to shoulder the burden of the core software (which they themselves commoditized by F/OSSing it) so that they could focus on SaaS (like AWS).
I'd like to think, Elastic's real problem is they have hard time competing with AWS in terms of pricing for SaaS (of course, AWS owns infrastructure and so it is a tough battle-front), but if they were paying any attention, AWS Elasticsearch Service was very poor in 2015 and continued to remain so for a long time (it sucks less now), but Elastic's own service wasn't up to the mark, either. I think they misplaced their priorities (see GCP's flawless execution with k8s, managed-k8s, and Anthos) and were caught asleep at the wheel when they could have captured SaaS market away from AWS in those interim years (2015-19) by focusing solely on differentiated features and not on the core Elasticsearch software (which was libre and hence undifferentiated).
Of course, Shay and Elastic know better than I do and I am indeed a grumpy developer who's upset, but I want Elastic to give up their misleading messaging viz. 'doesn't affect / nothing changes for our users'. They're being hypocritical and not doing anyone any favours.
> And to be clear, this change most likely has zero effect on you, our users. And no effect on our customers that engage with us either in cloud or on premises.
No, Shay. It does affect the community, who are also the users of the software.
> We created Elasticsearch; we care about it more than anyone else. It is our life’s work. We will wake up every day and do more to move the technology forward and innovate on your behalf.
I see a lot of "We"s and "Our"s. And that's the problem with CLAs and stealing someone else's work. Companies can't tell anymore who's stealing from whom.