3 ms·

Well the problems with conventional server side rendering (django, jinja, rails) are well documented (they're the reason (in part) people build react, angular e

Well the problems with conventional server side rendering (django, jinja, rails) are well documented (they're the reason (in part) people build react, angular etc.): * UI get's intertwined with logic and DB access * monolithic applications * UI developers have to have access to the full server side application I guess overall I wasn't suggesting this approach as an alternative to traditional django-eske apps, but rather to CRA-eske single page app platforms.

gregjor 6y ago
Django is not even a player. Look at Java, C#, and PHP, those are the big server-side tools. Rails, just barely. Logic and state are intertwined with UI in React/Angular apps, without the well-understood structure and techniques that can make server-side code manageable with clear separation of concerns. That happens because of the client-side frameworks, and limitations of focusing skills on the client side. Every server-side framework has supported templates for front-end developers, for a long time. There’s no reason someone focused on the UI has to know any more about the database and business logic working with traditional server-side rendering than they do with React or Angular.