|
|
|
|
|
by peterhunt
691 days ago
|
|
There's clearly something else going on here because I am having trouble following this argument. You pretty clearly laid out what you meant by server rendered in your original comment: > Were I forced to write a website today, it’d still end up looking similar to a traditional Django server-side rendering system with pages, and deep links, and all that. Nowhere did I advocate leaping to SPAs for no reason. I simply made the case - and stand by it - that building with the same set of technologies client and server side leads to more flexibility and less code. Re: the comment about booting the app, I think that is one of the strongest arguments in favor of server rendered apps, which is why I qualified my comment to "interactions", which happen after the page loads. I lived through the server-rendering-only days of the original Hotmail client, and the php-plus-jquery spaghetti era. They were terrible for developers and terrible for users. Going backwards would be a huge mistake. |
|
I didn't write this. You're confusing me with someone else.