Elixir's Phoenix is where a few former Rails folks have migrated to, so it shares a few of the ideas that made Rails so appealing: https://hackernoon.com/phoenix-is-better-but-rails-is-more-p... A list of companies using Elixir/Phoenix: https://github.com/doomspork/elixir-companies Discussion on how Bleacher Report (1.5B pageviews/month) moved from Rails to Phoenix: https://news.ycombinator.com/item?id=13606139
I used to work at a company in a similar vertical as BR also linked off CNN frequently and also running Rails. I understand the scalability challenges that might lead someone to something like Erlang and Elixir.
Curious, what’s your take on why this hasn’t caught on?
I think it is easier to find resources to answer rails questions though.
In addition, many of the languages you list are very young and their frameworks lack the maturity of something like Rails, Django, Spring, or Laravel.
I think it's worth asking, why are you looking to switch? If rails is not a performance barrier for you, then I do not see a good incentive to switch other than wanting to learn something new.
Laravel (PHP) is very Rails like. I love Rails but clients/projects have pushed me toward using Laravel the past few years. It's been a great experience. Lots of great packages, great community, great tools for deployment Forge + Envoyer. Laracasts.com is a great resource to see what it's all about.
I have not looked into Elixir Phoenix but have been hearing some noise about it recently. Folks also frequently compare Rails to Django (Python) ... my 2 cents is Rails has a lot of good tools to build web apps fast and underneath it all provides a lot of strong functionality. Most things are relative though to the specific "thing" you're building so I can not say Rails is the best framework without knowing xyz, but for most web applications I'd stick with Rails. You get a lot that often gets taken for granted. Nowadays it seems folks take 1 month bootcamps and come out thinking they know everything and are so quick to try the next framework. I think that bad implementations, lack of expertise, and biased opinions has hurt the public opinion on Rails. Ultimately Rails enables you to quickly build and figure things out. Once your business is set in stone, the data model is consistent, and you're no longer figuring it out you can switch focus outside of something like Rails and break your system up into solid super fast micro-services. It's just my biased opinion since Rails is "easy" for me. Perhaps Elixir or Django are just as nice, but ultimately I guess it boils down to the developers themselves, the mentorship, the team etc. Ruby isn't dead but if in 2017 developers are banking on 1 language or framework then good luck. Full-Stack problem solvers is becoming a norm now. Just figure out how to become a strong developer in general and care less about frameworks that most people / companies abuse and implement incorrectly all the time. Sorry for the rant but God Damn this Ruby is dead buzz is so annoying, irrelevant, and usually backed by people using it incorrectly in the first place.
Laravel (PHP) is very Rails like. I love Rails but clients/projects have pushed me toward using Laravel the past few years. It's been a great experience. Lots of great packages, great community, great tools for deployment Forge + Envoyer. Laracasts.com is a great resource to see what it's all about.
Nooo.. But then I have to use PHP.. I kid, I kid ;)
I have not looked into Elixir Phoenix but have been hearing some noise about it recently. Folks also frequently compare Rails to Django (Python) ... my 2 cents is Rails has a lot of good tools to build web apps fast and underneath it all provides a lot of strong functionality. Most things are relative though to the specific "thing" you're building so I can not say Rails is the best framework without knowing xyz, but…
Great rant. In a way my question is a challenge the Rails is dead noise. Maybe I’m an old dog but the stuff I see lately misses the mark. Developers seem to spend a lot of time thinking about how they’re going to run their microservices before any functionality is built... there’s something wasteful there. Rails just works and seems to be faster to solution than any of the piecemeal approaches I see in the microframework world.