> On Jun 2, 2015, at 2:43 AM, Emil Stenström <[email protected]> wrote: > > On Tuesday, 2 June 2015 05:19:43 UTC+2, Bobby Mozumder wrote: > At this point it’s probably easiest for Django to provide templates only for > Javascript front-end, and for Django to only serve API endpoints. > > We really don’t need Django to serve HTML pages anymore, except for the > initial page-load. > > In 2012, Twitter posted in their engineering blog about their conclusions of > trying to move all rendering to the client. It was just too slow. The answer, > and what is considered "best practice" now, is to render everything on the > server the first load, and render all subsequent page loads to the client. > This also means you get a nice fallback for clients that don't support > javascript. >
Yes, my expectation is that Django still only serves API endpoints, with something like Node.js & Ember Fastboot serving pages. Ember's Fastboot would make for an ideal candidate as a starting point for a new design for Django’s template view layer. -bobby -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6C44F42E-9BDD-4DEE-A6F0-937E95D55C5E%40gmail.com. For more options, visit https://groups.google.com/d/optout.
