The conversation

Lessons learnedExperience excerpt · English

I jumped ship from JavaScript and Typescript and I couldn't be happier

I jumped ship from JavaScript and Typescript and I couldn't be happier. I had no prior functional programming experience besides my abysmal short-lived experience with Haskell many years ago. > The barrier to entry is gigantic. Learning a new language using a different paradigm is a barrier, but I don't think it's gigantic. It also pays off in productivity once you get a good grasp on it. > The lack of up-to-date resources doesn't help. This is somewhat true, there are definitely orders of magnitude less third party resources available for Elixir/Phoenix than JS/TS/PHP, however I think high quality first party documentation makes up for it. I also think that 3rd party resources that do exist are on average higher quality than those that exist in other ecosystems. Learning resources: https://elixir-lang.org/learning.html Elixir in Action was my first introduction to the language after watching this talk[1] and I thought it was fantastic. I learned Phoenix mostly through reading the official documentation which comes with plenty of examples. …

Original discussionPhoenix 1.7.0 Released: Built-In Tailwind, Verified Routes, LiveView Streams166 source comments · at import
2

What was this responding to?

Parent context · original excerpt

LI

If you are an Elixir (or perhaps Clojure) expert, the following doesn't apply. But every other person jumping ship from, for example PHP or JavaScript should think twice. I think Phoenix is overhyped a lot. The barrier to entry is gigantic. The lack of up-to-date resources doesn't help. It's definitely not as polished as Laravel for example. And while there is Pragmatic Studio with their wonderful introduction video, there is nothing like Laracasts where there are new tutorials added all the time. Frankly, it's on another level. Deploying Phoenix is a nightmare when compared to Laravel. In Phx you have to reinvent a lot of things and often, of course, choosing the wrong path. Sure try the chat demo apps Phx is famous for but beyond that it's a pain in the ass unless you are very good Elixir programmer and can bug fix and reinvent-the-wheel things out. Also, Phoenix is bad in environments…

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

BO

> In practice this might mean reading the API documentation and writing 20 lines of code per endpoint - not a deal breaker for me. On this note, I have found Elixirs built in Task/GenServer/Process/Supervision primitives [sic] (also GenStage!) to be immensely useful when corralling diverse APIs. It's very easy to break each part into its own tiny system and link together, handle fails, backoff, etc.

Full original
LI

> not a deal breaker for me. The last two words "for me" is what I am talking about. The average web developer doesn't invent new libraries. He uses them.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.