nirmalc

If your use case is faster search - ES cloud is way more efficient/performs better than AWS. They manage their cloud stack pretty well. I hate those `amazon.internal` stack trace in thread stack ( when you try to troubleshoot something in prod) as you have no access to code to see what it even does.

Aws/amazon employs lucene contributors ( including Mike Mccandless). Not sure if amazon sponsors their work.

I don't think it's because of tech jobs. But it is true that there is serious shortage of coconut harvesters in South indian states. The job is not very well paid compared to risk ( coconut market itself is not very stable and rewarding). Not sure if there are any good occupational accident insurance policies available to them.

He mentions about that here : https://www.ge.com/news/reports/try-this-at-home-this-kid-bu... "I also happened to find the highly-detailed Air India seat map online, which made it easier to design the interior."

Im afraid its a bit over simplification . For example - Aggregations in elasticsearch are not using lucene facets, but it just leverages the basic lucene mechanisms ( collector) .

Project fi chat widget - always worked for me ( at least 5 times )

Ditto . "Just works " doesn't seem to apply when itunes is in picture

I would echo the statement. May be more than languages programming paradigms take more time to learn .