4 ms·
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 create
by joelbluminator 6y ago
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.
- RandoHolmes 6y agoElixir 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.
- joelbluminator 6y agoBased on the one comment from the one guy - talking about one app that might be not even Phoenix - it's definitely not an issue.
- AlchemistCamp 6y agoIt 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.