News for hackers. Stuff that matters.
Re:Amazon: Not OK – Why we had to change Elastic licensing by delfinom on Tuesday January 19, 2021 @10:51AM (#25834619)
Amazon is executing EEE in modern times, it's brilliant nobody sees it.

They are moving onto the "Extend and Extinguish" phase with elastic.

Re:Amazon: Not OK – Why we had to change Elastic licensing by ec109685 on Tuesday January 19, 2021 @11:12AM (#25834855)
Elastic is a 10B company and have the ability to write all the proprietary code they want to compete with Amazon.
Re:Amazon: Not OK – Why we had to change Elastic licensing by paxys on Tuesday January 19, 2021 @12:23PM (#25835868)
$15B actually
Re:Amazon: Not OK – Why we had to change Elastic licensing by chikens on Thursday January 21, 2021 @02:19AM (#25856394)
Don’t forget the CEO has cashed out ~$200M in stock the last two years alone and still holds $1B worth of stock, yet complains about AWS making money and changes the license so he can make even more. He likes to quote a tweet from 2015 from the CTO of AWS when they launched the Elasticsearch service in AWS. That was 6 years ago! They have had time to build a better offering with heir commercial licenses have failed. Elastic is trying to sell security now, what happens when they lose there too, change the license so any SIEM or analytics vendors have to pay them too? Elastic made a promise that the code would ALWAYS be Apache 2.0 and they went back on that promise, they lied to the community that helped build it, their customers, employees, partners and investors. The blog post about the license titles “Doubling Down on Open” is an insult to peoples’ intelligence, they are trying to play the victim because AWS is a mean bully. Well that’s business, if the CEO/founder didn’t see it coming then maybe he shouldn’t CEO? Take his billion dollars and go start something else and hand the company leadership over to someone who knows what they are doing.
Re:Amazon: Not OK – Why we had to change Elastic licensing by tootie on Tuesday January 19, 2021 @11:26AM (#25835060)
I don't see this at all. The "extinguish" phase is usually done when a product is acquired by a direct competitor to acquire it's customers. Amazon doesn't have a competing product. And their platform is well-known for supporting multiple competing software products (look at their array of databases for example). And the fact that they are now supporting their own JVM to protect users from Oracle's newly aggressive licensing.

This is, perhaps, exploitation but it seems unlikely they'll kill Elastic ever.

Re:Amazon: Not OK – Why we had to change Elastic licensing by dayjah on Tuesday January 19, 2021 @11:01AM (#25834740)
Sorry, what is “EEE”? Brief search turns up a horse disease?
Re:Amazon: Not OK – Why we had to change Elastic licensing by detaro on Tuesday January 19, 2021 @11:02AM (#25834751)
Re:Amazon: Not OK – Why we had to change Elastic licensing by mden on Tuesday January 19, 2021 @11:04AM (#25834777)
Embrace, Extend, Extinguish. Infamous strategy of Microsoft esp in the 90s.
Re:Amazon: Not OK – Why we had to change Elastic licensing by delfinom on Tuesday January 19, 2021 @11:05AM (#25834787)
One of the things Microsoft got anti-trusted for back in the day
Re:Amazon: Not OK – Why we had to change Elastic licensing by VoxPelli on Tuesday January 19, 2021 @10:57AM (#25834688)
They seems to be a lot better when it comes to cooperating with eg Envoy and Kubernetes communities though?

Not sure how good they are with eg MySQL and PostgreSQL, anyone know?

Re:Amazon: Not OK – Why we had to change Elastic licensing by detaro on Tuesday January 19, 2021 @11:04AM (#25834771)
communities is the key word. Neither have one company behind them whose income they are eating.