856 karma · joined December 6, 2009
Frequent speaker and author on tech subjects. Expert in building, scaling and maintaining complex web applications with Python, Django, React, PostgreSQL usually on Kubernetes.
Email: frank@revsys.com Twitter: @fwiles Mastodon: https://frankwiles.social/@frank Homepage: https://www.frankwiles.com/ LinkedIn: https://www.linkedin.com/in/frankwiles/ Work: https://www.revsys.com
Django is frontend agnostic so you can use whatever flavor of the month you like. (For better or worse hahaha)
Update: To be clear, I think Rails is a fine choice. I just don't think there is much of a reason to use it over Django these days unless you already know Ruby and don't know Python.
The hard part I find is not making myself a bottleneck on either the business or tech side because of me working on the other. It’s definitely a balance.
Couple decades ago even wrote some init scripts in Perl because they needed to be complicated.
By that I mean, entirely API driven, declarative, etc.
Definitely suffers from some of the challenges mentioned above (commercial clustering, large-ish frontend libraries, etc) but it's been pretty straight forward to work with and scales up well enough for our needs (a few hundred to a few thousand simultaneous concurrent players).
Usually the only friction is if there is a third party library/app you're using that doesn't yet support the newer version of Django.
It definitely saved a few peoples limbs at that company alone.
I and other DSF/Django members will likely be around here to answer any questions anyone may have.
My biggest hope is that this isn’t seen as scary or concerning to anyone. It should not be scary to any current users or contributors to Django.