It’s the part of ruby that replaced perl. For whatever eldritch horror perl was it was very, very good at doing text manipulation, and IME the only language to really match that experience was ruby.

I don’t get the downvotes. I’ve hired probably 30+ engineers over the last 5 or so years, and have been writing code professionally for over 20, and I fully agree with your sentiment.

In addition to iroh there is https://github.com/earthstar-project/meadowcap-js and other projects under https://github.com/earthstar-project. See https://willowprotocol.org/more/projects-and-communities/index.html#projects_and_communities

It varies on who does the interview but I push for much simpler than leetcode type stuff- e.g. not puzzle problems but more “design a program that can represent a parking structure and provide a function that could be used for the ticket printer to determine where a new car should park, as well as one that can run upon exit to determine payment”

Then if they are actually solid we can dive into complexity and optimization and if they can’t write a class or a function at all (and esp if they can’t model a problem in this way) it’s really obvious.

I’m betting you aren’t involved in hiring? The number of engineers I’ve interviewed with graduate degrees from top universities who are fundamentally unable to actually write production quality code is mind-boggling. I would NEVER hire somebody without doing some panel with coding, architecture/systems design, and behavioral/social interviews.

Thanks this matches my understanding too (erlang is all about actor model is my understanding, similar to akka)

Thanks that’s helpful and maps to how I’m thinking it might be useful

I found the art of prolog 2nd edition and starting reading this…

It got this foothold pre-spark, largely due to the akka and typesafe/lightbend ecosystem. Then spark resulted in a lot of data engineers picking up scala (this was my entrance, from the Hadoop map/reduce world). And now cats/zio and effect systems have rounded it out.

Personally I love scala, my teams use it heavily (mix of styles but mostly zio-http, and a lot of spark). But scala3/dotty has been problematic enough for us that we decreed people stop updating their apps. The learning curve is HIGH (esp for functional/effect system scala). The candidate pool is small. I don’t know that if I were to start a greenfield project (without all the rest of the platform already using it) I would suggest we use scala. But the rest of our platform does, and we have tooling, and L&D tracks, etc. So onwards we go.

https://mutatest.readthedocs.io/en/latest/