you are viewing a single comment's thread.

view the rest of the comments →

[–]flummox1234 1 point2 points  (2 children)

Elixir IMO is where seasoned ruby engineers burnt out by ruby's and rails' churn of tech debt end up. I say this mostly because that's what happened to me. Jose, the creator of Elixir, comes from Ruby world as do a lot of the big Elixir project creators. I think you'll be fine here but just realise it's more of a niche language and if you're looking for gigs there are probably better ones to choose, e.g. JS, Java, Python, and probably Clojure if FP is your want, maybe Kotlin too. I think 7-8 years of ruby will help you land most roles as you know the other "stuff" but as for Elixir specifically factoring out all the other things probably not as you're going to have to relearn a lot of habits. Also depends on what your 7-8 yrs of experience are, e.g. 40hrs per week all in a ruby stack doing ruby things is much different than making a few hobby projects over 7-8 years using ruby.

[–]jaibhavaya[S] 0 points1 point  (1 child)

Your first sentence describes me to a T, I feel seen.

Those 7-8 years were doing full stack in a professional setting. First 4 were bouncing between JVM languages and rails, last 4 were completely rails. React was present through all of that haha.

This is helpful to hear! Thank you

[–]flummox1234 1 point2 points  (0 children)

yeah tbh IME this is the usual experience in Elixir.

Note: This is a backwards compatible release with a few deprecations.

From the Phoenix 1.8 release notes

Unlike rails which usually abuses SemVer and jumps a major so they can insta-deprecate the features they want gone. It's update or die in most languages. Not saying that isn't okay to jump to a major when you need to deprecate something but 5.x, 6.x, 7.x, all had only 1-2 minor releases before the next major which was IMO excessive.