My company is moving away from it. We built a few services but after a few years some of the original people that introduced it left the company and it became very difficult to hire for. New hires were either people wanting to learn (so we had to spend a good bunch of resources into teaching + end up with a system built by noobs to the language) or very expensive developers with a lot of experience in erlang and elix…
oh boy. where to begin > We built a few services So you never really committed to it in the first place. Also, this complicates the deployment problem. > after a few years some of the original people that introduced it left the company Probably left for a company that actually committed to Elixir. :P > and it became very difficult to hire for In a world where everyone is remote and where 10 Elixir people apply to eve…
That's really inaccurate, not everyone is remote and looks like post COVID most companies will be hybrid office/remote. So hiring is still a problem, and getting hired is a problem for people who don't want to be 100% remote.
> "We can underpay cheap devs again"
I don't think Rails devs are particularly cheap though I'm not sure if that's what you meant.
> mutation bugs, monkeypatch bugs, and concurrency bugs (just forget running your test suites in parallel)
Rails comes with parallel testing since Rails 6. As for concurrency - I know that Gitlab moved to Puma (a threaded webserver) and tons of huge companies use Sidekiq which is threaded as well. I'm not saying there are never any problems but it seems to work well for many many companies.