4 ms·

I tend to agree with most of what you're saying, but one thing that leaves me conflicted is that with a document model, don't you lose the personalization of th

I tend to agree with most of what you're saying, but one thing that leaves me conflicted is that with a document model, don't you lose the personalization of the content? One of the reasons Netflix or YouTube is so slow is because every time you load up the page, you're supposedly getting a page that's full of content targeted specifically for you. Would you say that you just don't want the personalization?

chubot 7y ago
Why do you think you lose personalization? That's an independent issue. I don't mean the site is completely static. I mean the site is rendered on the server, like how 99% of websites worked before 2010 or so, including Google's. Those sites were personalized. A shorthand for the argument is jQuery vs. React. jQuery enhances a document; React "takes over" the page to give you an app. There are limitations of jQuery which is why I didn't say that specifically, but that's the general idea. ---- I'm finding in the last 5 years that people "forgot" how websites were made. It seems like the "default" mode of thinking switched to SPA. SPA makes some things more convenient and other things less convenient, but it's totally independent of functionality, like whether the site is personalized or not. Ironically SPA seems to be so slow that people now render it on the server, which is totally bizarre to me. ---- Update: This comment in the same thread goes into the issue of state management, and performance: https://lobste.rs/s/jmmr3w/interview_with_drew_devault#c_6ppu3t https://lobste.rs/s/jmmr3w/interview_with_drew_devault#c_6pp... There's a legitimate reason for the SPA architecture, but it comes with many downsides as well. Good article (which is ironically on Medium, a great example of a document turned into a terrible, slow app): https://medium.com/@addyosmani/the-cost-of-javascript-in-2018-7d8950fbb5d4 https://medium.com/@addyosmani/the-cost-of-javascript-in-201... https://news.ycombinator.com/item?id=17682378 https://news.ycombinator.com/item?id=17682378

chubot 7y ago

Why do you think you lose personalization? That's an independent issue. I don't mean the site is completely static. I mean the site is rendered on the server, like how 99% of websites worked before 2010 or so, including Google's. Those sites were personalized. A shorthand for the argument is jQuery vs. React. jQuery enhances a document; React "takes over" the page to give you an app. There are limitations of jQuery which is why I didn't say that specifically, but that's the general idea. ---- I'm finding in the last 5 years that people "forgot" how websites were made. It seems like the "default" mode of thinking switched to SPA. SPA makes some things more convenient and other things less convenient, but it's totally independent of functionality, like whether the site is personalized or not. Ironically SPA seems to be so slow that people now render it on the server, which is totally bizarre to me. ---- Update: This comment in the same thread goes into the issue of state management, and performance: https://lobste.rs/s/jmmr3w/interview_with_drew_devault#c_6ppu3t https://lobste.rs/s/jmmr3w/interview_with_drew_devault#c_6pp... There's a legitimate reason for the SPA architecture, but it comes with many downsides as well. Good article (which is ironically on Medium, a great example of a document turned into a terrible, slow app): https://medium.com/@addyosmani/the-cost-of-javascript-in-2018-7d8950fbb5d4 https://medium.com/@addyosmani/the-cost-of-javascript-in-201... https://news.ycombinator.com/item?id=17682378 https://news.ycombinator.com/item?id=17682378