5 ms·

Elastic isn't really an OpenSearch competitor if you want an open source solution. When I check their Github, I see recent commits, merged pull requests etc. D

by gkbrk 3y ago

Elastic isn't really an OpenSearch competitor if you want an open source solution. When I check their Github, I see recent commits, merged pull requests etc. Doesn't look half-dead at all. I don't know if other open-source alternatives (like meilisearch perhaps) have more activity, but OpenSearch looks far from half-dead. > in a just world Amazon wouldn't have been allowed to call it "OpenSearch" Any reason an open-source project for search should not be called "OpenSearch", aside from "I don't like Amazon, so the project is bad"?

BoorishBears 3y ago
[flagged]
BoorishBears 3y ago
> Any reason an open-source project for search should not be called "OpenSearch", aside from "I don't like Amazon, so the project is bad"? If you want to pretend that the thought process was "open source search" => OpenSearch you're free to do that. The rest of us realize the project exists because they were unfairly benefiting from the Elasticsearch trademark and got push back... So naming it "OpenSearch" then mentioning Elasticsearch 70 times in your FAQ https://opensearch.org/faq/ https://opensearch.org/faq/ isn't a coincidence: they want to drive the same kind of confusion they got called out on in the first place.
- capableweb 3y ago
  > The rest of us realize the project exists because they were unfairly benefiting from the Elasticsearch trademark and got push back... Wasn't Elasticsearch initially 100% FOSS and you were allowed to sell it as a service? Where is the "unfairly benefiting" part coming from?
  - BoorishBears 3y ago
    Amazon lied about partnering with Elastic, stole Elastic's closed source extensions by proxy, and used Elasticsearch's trademarked name without permission FOSS doesn't mean you can steal their name, even in the purest forms of open source. And the irony is AWS has mountains of closed source components that would benefit others to actually productize "OpenSearch". Under SSPL Amazon would be able to serve Elasticsearch... if they were willing to walk the walk and open source the stuff that enables their orchestration.

by gkbrk 3y ago

BoorishBears 3y ago

[flagged]

BoorishBears 3y ago

> Any reason an open-source project for search should not be called "OpenSearch", aside from "I don't like Amazon, so the project is bad"? If you want to pretend that the thought process was "open source search" => OpenSearch you're free to do that. The rest of us realize the project exists because they were unfairly benefiting from the Elasticsearch trademark and got push back... So naming it "OpenSearch" then mentioning Elasticsearch 70 times in your FAQ https://opensearch.org/faq/ https://opensearch.org/faq/ isn't a coincidence: they want to drive the same kind of confusion they got called out on in the first place.

capableweb 3y ago
> The rest of us realize the project exists because they were unfairly benefiting from the Elasticsearch trademark and got push back... Wasn't Elasticsearch initially 100% FOSS and you were allowed to sell it as a service? Where is the "unfairly benefiting" part coming from?
- BoorishBears 3y ago
  Amazon lied about partnering with Elastic, stole Elastic's closed source extensions by proxy, and used Elasticsearch's trademarked name without permission FOSS doesn't mean you can steal their name, even in the purest forms of open source. And the irony is AWS has mountains of closed source components that would benefit others to actually productize "OpenSearch". Under SSPL Amazon would be able to serve Elasticsearch... if they were willing to walk the walk and open source the stuff that enables their orchestration.