31–40 of 144 posts
Earlier quoted context omitted.
Revenue only tells us how much business they conducted, not how much of a "killing" they made. Profits is what would tell you that, which I guarentee are going to be far less than their $177.6 million in revenue.
You don't have to guess: they're a public company. https://finance.yahoo.com/quote/ESTC/financials?p=ESTC
Can't Amazon just serve these bogus headers and keep opensearch compatible? It's not like headers are copyrighted...
> If call to '/' fails with 401 or 403 pass the check and show a warning (message will be linked later). This happens if the monitor permission missing for user. The subsequent checks must be ignored.
Can't Amazon just serve these bogus headers and keep opensearch compatible? It's not like headers are copyrighted...
Hacker News had a good discussion about this earlier today. https://news.ycombinator.com/item?id=28103389 What surprised me was how many commenters seemed unhappy with Amazon's Open Source alternative and the level of resources they appeared to be committing to it.
This should be forked to be opensource compatible. Opensource doesn't mean that you get to control everything. If what you're offering doesn't stand on its own merits then what's it worth? I get that we wish Amazon couldn't do what they do but that's what the license permits.
PostgreSQL should be everyone’s first choice for a data store. It can do so much, including serving as your full text search system.
I love postgres and the full-text search feature works great in some use cases, but it is not really comparable to elastic search in many scenarios (huge document stores, complex text processing or querying, etc).
Instinctively I believe what you're saying, just wondering if you know for sure.
Can't Amazon just serve these bogus headers and keep opensearch compatible? It's not like headers are copyrighted...
Amazon could try that, but it wouldn't stop there. they'd end up in a constant arms race. also, that "you know, for search" tagline is featured on t-shirts sold by Elastic [0]. seems entirely plausible to me that Amazon & Elastic lawyers could get into a pissing contest about potential trademark or copyright protection of that term and whether sending it as an HTTP header constitutes infringement. 0: https://elastic.…
PostgreSQL should be everyone’s first choice for a data store. It can do so much, including serving as your full text search system.
However, it does get one up to that 80% mark for text search. But that other 20% is why Elasticsearch and Algolia etc exists.
Earlier quoted context omitted.
It is easy to judge another’s actions from afar when it’s their meal and roof they’re working for. It’s okay for Amazon (a trillion dollar company) to make money off of their work but not themselves? Imho, the problem isn’t “well it’s not open source anymore then.” The problem is people who give more weight to a religion/philosophy than sustainability. Who cares if it’s open source if the people developing it can’t s…
If they don't like it, they shouldn't have licensed their software under a free software license. This was an entirely foreseeable consequence. They only have themselves to blame. The AGPL generally fixes this perceived problem, but means that several large players (like Google) will never touch your code with a ten foot pole, let alone improve it. So, there's some difficult decision-making at the inception stage of…
They or anyone else are also free to relicense their project, there's nothing wrong with it at all and anything under the old license is still what it was before.
It seems kinda strange to demand that someone operate under some license in perpetuity, there is no such rule. Licensing questions don't stop after the inception of a project.
Earlier quoted context omitted.
I love postgres and the full-text search feature works great in some use cases, but it is not really comparable to elastic search in many scenarios (huge document stores, complex text processing or querying, etc).
Do you know for sure that postgres doesn't perform as well as elasticsearch if you don't use the relational capabilities of postgres? Instinctively I believe what you're saying, just wondering if you know for sure.
Elastic search and other search solutions don’t have this problem.