Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Licensing changes to Elasticsearch and Kibana

elastic.co

Post reply on HN
Print view View original

371–378 of 378 posts

Re: Licensing changes to Elasticsearch and Kibana

#371

Post by pjmlp »

Drdrdrq wrote: post #363
pjmlp wrote: post #303

Earlier quoted context omitted.

Yeah, that is what happens when one turns down the opportunity to own Java.

Are you saying Google did that? Any links?

When Sun was put on sale, there were eventually two offers, Oracle and IBM (which withdraw theirs shortly thereafter).

Google did zero offers back it was still unclear who would save Sun, most likely hoping that they would just sink away.

Eventually Oracle and IBM came into the picture, and still radio silence from Mountain View.

So yeah, they get what they deserve.

As for links, the press of the day.

Re: Licensing changes to Elasticsearch and Kibana

#372

Post by poobears »

The big problem I have is that in their marketing material up to this point they stated “Apache 2.0: Now and always”. They had two lawsuits they filed against competitors, both AWS and SearchGuard because they have basically been making money off of Elasticsearch. I don’t think those lawsuits are going well so they changed the rules, and will likely do so again if they lose money to competitors. I don’t trust them, in particular I don’t trust their founder and CEO. He lied to the community and is cashing in in the community’s work.

Calling the blog post “doubling down on open” is an insult to the community’s intelligence. They should be more “open” and honest about what their doing and why instead of playing the victim.

Re: Licensing changes to Elasticsearch and Kibana

#373

Post by jaymee »

__blockcipher__ wrote: post #278
wmf wrote: post #184

Earlier quoted context omitted.

That's great for Matt, but other companies like Elastic can't afford to go from >50% to 5% of their market.

Well, now organizations like Wikimedia are going to have to drop Elasticsearch everywhere despite it powering wikipedia article search and more. So congrats on both missing the GP’s point and also failing to see how this license change would shrink Elastic’s usage / market anyway

They don't need to drop. They're not providing Elasticsearch and Kibana as a paid service to others. You can just read the FAQ: https://www.elastic.co/pricing/faq/licensing Using Elasticsearch and Kibana is still free, unless you're selling them as a service like AWS Elasticsearch does.

Re: Licensing changes to Elasticsearch and Kibana

#374

Post by akshaykumar90 »

z77dj3kl wrote: post #186
jabo wrote: post #68

Earlier quoted context omitted.

Adding Typesense to the list as an easier-to-use alternative to ElasticSearch: https://github.com/typesense/typesense One thing to point out though is that Typesense, MeiliSearch (and Algolia) are designed for Instant Search experiences, and so hold the entire index in memory. So for petabyte scale data (like logs) it might be wasteful (and expensive) to store that size of data in memory. This is where ElasticSearch…

Do you really have to spam your project on every thread even remotely related?

If it is even remotely related, it is not spam.

Re: Licensing changes to Elasticsearch and Kibana

#377

Post by croes »

cutemonster wrote: post #365
9dev wrote: post #344

Earlier quoted context omitted.

By very definition, it cannot be "end to end" encryption if it isn't encrypted from one end to another.

Here's a way to build true e2e encryption apps that can be, to some extent, censored: NLP locally in the phone -- an AI that slightly understand what the user writes -- and if it's (I'm oversimplifying) like "kill all ...", then the AI bricks the phone. Otherwise it's e2e as usual.

An AI that understand what the user writes? We are far away from that. "All my service processes hang." "Kill all" Bricked
Post reply on HN