Ask HN: Are you satisfied with Elixir or do you regret choosing Elixir?
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 elixir.<p>We also found many times missing libraries, or found libraries which are incomplete, or unmaintained or just not well documented. Just compare the total amount of libraries in Hex, vs the total amount of libraries in rubygems. Somebody will say &quot;but Elixir libraries are higher quality so we need less, etc,etc&quot; as if there were not good developers in the ruby world and every elixir developer were a rockstar.<p>Tooling is just terrible. The VSCode plugin is crap, kills the CPU unless you disable features. There is no IDE from jetbrains. There is a plugin but last time I tried it, it was even worse than the VSCode plugin.<p>Also, I&#x27;ve read some comments where people mention &quot;we don&#x27;t need redis&quot;, &quot;we don&#x27;t need workers&quot; everything is so much easier. That was our thinking at first. But then you realize on deployments you will lose your cache, or your background jobs, etc. So you have to persist them either in mnesia or in the database. At that point you&#x27;re just reinventing your crappy undocumented and untested version of delayed_job.<p>Most of what you get from elixir in terms of redundancy, high availability, etc you can have that anyway from kubernetes, heroku or any PaaS.... you will need more than 1 server anyway, so...<p>Liveview sounds amazing until you try to use it in the real world. The most minimum latency kills the experience.<p>In the end, we are back to Rails and much happier. Specially now we are using all the hotwire stuff. Not fancy, and not fashionable though.