Yes, it does. It has been around much longer and the Python ecosystem is very large.
That being said, the Elixir community has been my favorite community of developer. I haven’t been stumped yet thanks to the help of many people on this forum much more intelligent than me.
I also prefer frameworks like Flask, CodeIgniter and Sinatra over Django, Laravel and Rails. You know more about how your app works when you use these frameworks.
I did Flask.
It’s very very bare bone, there was no real convention for where you put certain files. It reminds me of express.js framework.
I’ve found myself spending too much time figuring out how I want my code to be organize and it was frustrating when I just want to code the logic. There is always this frustrating and fun feeling of I can improve this by breaking these code up and doing this and that.
Phoenix is much more opinionated and organized. There are only few complaints, one was organizing custom plugs and such. I ended up creating a plug folder in app_web and all plug have a namespace appweb.plug.myplug. But this is also due to me being new to the language and framework.
Where your files exist on disk (at rest) is much less important than how your code interacts at runtime (in motion).
I mean all things being relative, me having to inherit a flask code base with 5000+ or so lines of code in app.py, but I guess your right code interacts at run time is much more important.
What does (at rest) mean?
+1. The “at rest” code is much more important on a maintenance perspective. I much prefer opinionated frameworks for that alone, even when I would have preferred to handle it differently, as it is much easier to get started, to understand others’ code bases to get ideas and solutions, and to transfer the ownership of the code (including to my future self two years down the line).
I’ve been working with Django since version 0.9x. So for quite some time now.
There are several things I really like about Django:
The downside is that concurrency related tasks are very hard to do and requires workarounds like job-queues etc.
Especially the concurrency issues are what brought me to Elixir. And so far I am pretty happy with Elixir/Phoenix. For me the most noteable differences where:
I’ve been feeling this as well. Each library’s doc taken individually is great, but when trying to add a metric for available DB connections, I had to search in Ecto, Ecto SQL, Postgrex, DBConnection, Telemetry, Telemetry Metrics, Telemetry Poller, and Telemetry Statsd. I wonder if it would make sense to generate a “global” searchable help based on the current app’s dependencies or something…
(In the end, I didn’t find a supported way to get the number of available DB connections)
My impression in the majority of the responses is that Phoenix is great but not better than Django. Please help me decide where to focus on, vote if you will Phoenix or Django?