OK, stability is relative.
Compared to Node / Elixir Rails is still pretty stable. I'd put it with stacks like Laravel / Django.
ASP.net probably changes less, I agree. But .net core was a huge change though, kind of a new framework right? new runtime even.
I don't have any experience with Elixir / Pheonix.
From comments I read, even things like deployment change frequently in Elixir, and major libraries are created or abandoned.
It's just still a very new ecosystem.
In 5-10 years I'm sure the rate of change will decline.
Then there is a stack like Node where constant change seems to be just part of the culture.
Rails changes too, but not as much.
Elixir compiles and runs on BEAM, which is a technology that's roughly 34 years old.
I think most elixir projects are on Phoenix, and while I can't speak too much about the speed of that project, the poster you're responding too has clearly stated they have an app that's 4 years old and running just fine so I have to believe it's not as much of an issue as you think.
It was a Phoenix app. Upgrading from v1.2 to 1.5 is very straightforward, the largest part being replacing Brunch with Webpack for the front-end.
There are some new choices for building releases that make it easier for people who prefer to use run time environment mentioned variables for configuration instead of compile time ones. Previous ways of building releases still work as before.
I make releases with Distillery just as I did back in 2016. The main change in my release workflow is that now I use Gitlab CI/CD, and that's unrelated to any Elixir or Phoenix changes.
I don't know what that means in this context. What I do know is that RoR versions go EOL roughly 2-3 years after they're released. That's not stable by any stretch of the imagination.
