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.
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.
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) .
At some point, that's the motivation to keep learning the Nth one. You don't know what you don't know, but when you stumble into a new paradigm, it suddenly creates this massive perspective shift that changes how you use all the languages you already have learned.
Sure. Each language has its quirks, and bells and whistles. Starting with C, and then moving to Objective C, just the basic nomenclature and syntax makes you think of the architecture you're building in new ways.
C# has built-in facilities to call C++ code in a managed sense. C# doesn't do pointers the same way C does, so all of the low level minutae to pull that off is a very powerful feature.
There are even some microcontrollers whose architecture doesnt support function pointers very well, ao just doing vanilla C stuff is essentially hardware limited.
