I was working with first ElasticSearch versions when Shay was the only developer. At that time, I was impressed how Shay was responsive, friendly and overall ES had good design, compared to Katta [1] we used in our product.
ES was my go-to search engine since, but something fishy started to happen with elastic.co from 2018. They changed the license, started to use dark patterns for downloads and product names and this message from Shay, where he invites Search Guard users to use 'free security features' (which aren't free at all) from elastic.co, is low blow, not for Search Guard devs/users, but for ES users as well. If I develop a custom plugin for ES and charge support for enterprise users, how will I know they will not come after me simply because they have similar addon?
As one comment noticed, alleged code is too common and can be found in Lucene as well.
I'm hoping this will end well, but elastic.co brand isn't going to be the same.
(Also, elastic.co isn't immune to taking over other work as well [2]).
My thoughts exactly. I'd even say that Elastic is acting very toxic and childish, but then again, they IPO'd, dunno who's running the show now could be anyone for what I know.
It sure is someone who' eager for profit though, that's for sure.
ES was my go-to search engine since, but something fishy started to happen with elastic.co from 2018. They changed the license, started to use dark patterns for downloads and product names and this message from Shay, where he invites Search Guard users to use 'free security features' (which aren't free at all) from elastic.co, is low blow, not for Search Guard devs/users, but for ES users as well. If I develop a custom plugin for ES and charge support for enterprise users, how will I know they will not come after me simply because they have similar addon?
As one comment noticed, alleged code is too common and can be found in Lucene as well.
I'm hoping this will end well, but elastic.co brand isn't going to be the same.
(Also, elastic.co isn't immune to taking over other work as well [2]).
[1] http://katta.sourceforge.net/
[2] https://discuss.elastic.co/t/vector-modules-going-apache-xpa...
EDIT: added link to vector module issue