3 ms·
> It's also worth considering that the whole paradigm underlying Django and Rails, wherein you render a bunch of HTML with your choice of backend language, may
by legutierr 14y ago
> It's also worth considering that the whole paradigm underlying Django and Rails, wherein you render a bunch of HTML with your choice of backend language, may not last forever. With the client side getting heavier over time, the advantages of sharing code across client and server may push the mainstream away from Ruby and Python. Or not. This isn't a prediction; more like a "what if."
From that perspective, one thing that Django has going for it is the Django REST Framework (http://django-rest-framework.org/ http://django-rest-framework.org/), which is pretty great. Of course, it's probably the case that Ruby has something similar.
- jarrett 14y agoYep! Rails has a lightweight, API-oriented flavor. But even without the HTML templates--even if you're just serving up JSON or XML or whatever--you're still stuck with one language on the client and another on the server. What I'm really curious about is whether the advantages of having a single language on both client and server will ultimately outweigh all other concerns for most web projects. I have no idea what the answer to that question is.