Hacker News Reader

Comment by toolz | Hacker News Reader

I hear this all the time, but what exactly does the elixir ecosystem lack? It's older than the python ecosystem (open source release was much later), although not nearly as popular but since elixir can drop-in erlang libraries as easily as "native" elixir libraries (caveats exist) I'm not sure I find this statement to be nearly as correct relative to how often I hear it stated

View on HN

Parent is specifically talking about Django, and I'm not sure if there is anything comparable to Django in the Elixir ecosystem. So, if there is an absolute necessity for time-to-release at all costs, I reckon Django would probably have some advantage over Elixir.

Yeah, for some use-cases the Django Admin and everything-spawns-from-the-model approach can go from nothing to CRUD in a ridiculous time.

Phoenix is ludicrously quick to get from zero to realtime UI and interesting backend work such as polling, consuming updates, sharing state, collaboration.

Having done a bunch of Python I wouldn't discount Django but I would pick Phoenix almost every time at this point. The initial burst of Django doesn't seem like a long-term upside and Elixir/BEAM/Phoenix has a lot of long-term upside in my eyes.

And, by my estimate, Django has been around ~9 years longer than Phoenix.

Comparing DjangoPackages[0] and awesome-elixir[1], sure you could say "there's an elixir package for everything", but how battle-tested are they? How well-maintained are they?

If someone is trying to decide between Django and Phoenix, I am not sure how likely it is that the individual would have the necessary Elixir/BEAM experience to be confident in dropping-in erlang libraries.

[0] https://djangopackages.org/ [1] https://github.com/h4cc/awesome-elixir

Reply on news.ycombinator.com