IMHO the two main advantages in favor of Algolia, are the sane defaults for relevancy and speed and the fact that the service is hosted and can grow with your business without having dedicated engineers to manage both the configuration and the infrastructure.
Also, on top of the Algolia services per se (search, analytics, recommendation, etc.), we're providing a lot of backend and frontend libraries which one would otherwise need to reimplement when using an elastic- or Solr-based implementations.
Disclaimer: I'm maintaining the Java/Scala/C#/Go API clients at Algolia.
Exilir and Rust would indeed be great additions to our integrations. However, we are really cautious when considering to support new languages. As said in the interview, we try to provide those API clients in the most idiomatic way for each language.
At the moment, we do not have a lot of demands for those languages nor the necessary workforce to onboard on those two languages (only very few people are proficient with those languages at Algolia and we don't have any production code using them IIRC).
> Alternatively, awk '{print $2}' netflix.tsv would have given us the same result. For this tutorial, I use cat to visually separate the input data from the AWK program itself. This also emphasizes that AWK can treat any input and not just existing files.
Thanks to you... and OP! I have been using posix systems for years but never really touched awk because what I have seen have seemed like archaic chants of dark magic, very good resources for learning about this nifty tool.
[1] https://pixelastic.github.io/css-flags/