jerelunruh

I believe plenty of people do it for a leisure activity rather than to make a living. Sort of like putting puzzles together or surfing the web. Some workers may even be at a dull job (such as a tollbooth operator at night) and their boss doesn't mind.

All forward looking statements are guesses but... I see a strong movement toward Elixir from Ruby devs (and others, I'm not a Rubyist) and I expect Phoenix to be one of the main frameworks in the next few years. It's due to a combination of simplicity, history (erlang is old), and a change in the types of apps some of us are building. There will always be simple CRUD apps too but the demand for constant connectivity seems to be rising. IoT, desktop replacement apps, etc.

Edit: fixed typo referring to Elixir as a framework

There seem to be plenty that lean toward non-mainstream practices. However the one I go to was fully planning to have a career as an MD but converted to chiropractic after it helped him with his own health. He tells me that building core muscle strength is the long term solution, not constant adjustments.

I live in a rural area and have fiber to the home from our electric co-op. It's amazing: $99 symmetric gigabit and rock solid service.

On the other hand AT&T is the phone provider here and selling DSL is the least of their worries. One of my clients (a block from the phone switch office) needed DSL as a backup to their fiber connection and AT&T can't provide it because their "equipment is already full". As I see it that's the damage of a monopoly; luckily for us we have proactive co-ops that can compete on projects of that size or we'd have no wired internet.

From what I've read (I'm not an expert either) nginx is completely optional. Cowboy (used by Phoenix) supports https termination and I understand that it's the router for Heroku so it sees plenty of traffic.

Another Django -> Phoenix dev here. Currently I miss Django's model field types (UrlField, EmailField, etc) and will probably write them if no one else does soon. I sometimes miss South style migrations when I'm prototyping but doubt there's a good reason to implement them in Phoenix. For building JSON APIs JA Serializer is a quite capable alternative to DRF-JA.

For the Django Admin there's ex_admin which I haven't used yet but it appears to take a bit more work than the Django Admin does.

I haven't felt like virtualenv + pip was too bad for deps and deployment but exrm is already comparable/easier with an even better `mix release` planned for this summer/fall. No uwsgi or gunicorn to configure and even nginx can be skipped.

For the last part of your question: the biggest thing missing from Django was a good way to do websockets. Django has channels now but I doubt they'll work like Phoenix/OTP/Erlang (especially in the concurrency and fault tolerance categories).

Let's say that currently rent is $1,000 per month, food is $500, and Alice is earning $2,500.

Now UBI is implemented and Alice and all fellow citizens receive $1,000 per month. What will keep the market from easing the entry level rent up to $1,500 and food to $1,000 since the money is available? At first glance it seems like we'd just be choosing a different number representing "broke".

I tried every variation I could get to work including tornado, asyncio, and pypy. In my simple "how many websockets can I open" tests python would start erroring by 10,000 (no Django, just an empty websocket) while node hit 40,000 and was still climbing. Eventually I concluded it was a case of "with sufficient thrust pigs fly just fine". I still like python; just doesn't seem to be worth the effort to try to adapt blocking libraries into a non-blocking use case.

I use the same architecture... DRF for the API, admin for quick data manipulation, Ember for the interface and I enjoy it immensely. I am learning Phoenix because it would allow me to handle bidirectional communication in the same codebase along with other Erlang advantages. So far it doesn't seem to have anything comparable to DRF.