2 ms·
This is correct in general, but there is some detail missing. I wouldn't call myself an experienced Python developer, but it's my most comfortable language so
by rahimnathwani 11y ago
This is correct in general, but there is some detail missing. I wouldn't call myself an experienced Python developer, but it's my most comfortable language so I'll use that to illustrate.
1) I'm comfortable with Python, and have some understanding of web frameworks. Should I use Django or Flask or Pyramid? Which ones have a shallower on-ramp, or will help me make my project more modular?
2) It's 2015, should all web apps consist of a clean RESTful API, decoupled from the front-end? Or is it OK to have all server-rendered pages?
3) If I should separated as per point (2), then does that mean I should stick to a lighter web framework, instead of using Django+DRF to provide the API? How should I build the front-end? Backbone? React?
4) If I don't separate front and back-end, what do I do about the little things that need some Ajax magic? Just write some 'onlick=...' stuff in my templates? Or should I be keeping my JS modular and using gulp or something to collect stuff up?
Even if the answers is 'just use Django' or 'just use Rails', there are lots of specific things to decide, and it's annoying to have to do so. If I were a Ruby expert starting a web app tomorrow, at a minimum I'd have to decide between Rails and Sinatra, and between rbenv and RVM...
- cweagans 11y agoAt least you'd have the knowledge to make that decision intelligently and only have a few choices to make, rather than having the burden of learning an entirely new tech stack on the fly and likely make decisions that may not be the "right" way to do things with that stack.