This is highly subjective and argumentative. If you think different, please comment!
I love to develop highly interactive and complex apps - that run in the browser. I also think the browser is still the most important tool for accessing them. At least for now. And the next few years. Even on mobile.
Search engines can't find my app's deeper content. That's okay, it's only for members anyway. They still find my
index.html and that's fine enough for indexing.
Top comments (11)
Out of interest, what is subjective or argumentative here? All seems obvious to me ...
And yeah I agree with you on these shady subscription popups. Fortunately my apps don't have such dark pattern 😄
Really? Where do you see such a trend? I have if anything, suspected the opposite trend. To more and more client side code. The popularity of CDNs in delivering it is huge, because the likelihood that you already have JQuery, Bootstrap, React or whatever cached locally because most sites use the same CDN (cloudflare is huge) is quite high!
Not sure if Jan is referring the SSR everything people in JS community. I have seen a few people around Meteor demanding more SSR on par with Next.js and even in case of Next.js it seems weird to me. These are full JS apps.
In my use case besides index I also have a few other pages that I want to be able to index or be accessible enough for nice boxes on social media, but these days with a bit of help most search engines and social media handle that.
SSR puzzles me. I tend to transmit data to the client in far more efficient formats, typically JSON and have client side code to render it as desired. Also allows the client to alter rendering and have a load of options for rendering that involve no server round tripping. I'll take a look on-line as I'm curious about trends in this space, but I've never detected yet a trend to render HTML server side (that is the old school way, using static of PHP generated HTML - or even in its day Perl and other CGI related HTML production). The modern trend has been to create client side apps that request data from the server as need (AJAX), as far as I can tell.
True, from what I have seen people want SSR for SEO and to get them to render on client super quickly to satisfy Google metrics (hence SEO).
Actually looks like I misunderstood SSR? I just read this and it puzzles me immensely:
The difference seems very very subtle. Both seem to allow client side code, and they claim SSR simply provides the initial view so it can be seen while JS downloads while CSR doesn't (you see the view after JS is downloaded and renders it).
To be honest most of my experience is with templates that provide basic page layout and initial views indeed, and then interactive elements that need to respond to changes in data are rendered by client side JS, generally filling in spots left blank in the original template.
But to be honest I wonder about this whole "while JS downloads" as the real experience I have 95% of the time, maybe 99% of the time is that this time is negligible. And that would be because the bulk of the JS (the libraries) is locally cached already due to either my earlier visit or being standard shared CDN delivered library material. Heck most of the delays I get in page presentation are server side costs generating the data, but then I have some complex data I work with, spanning many tables and relations etc in an RDBMS ;-). But to speed that up I manage my own server side caches too (as does any site really) so that once a given view is generated it's available quickly for some while thereafter or until invalidated.
Still, I cannot imagine anyone disabling JS generally unless they are content with a tiny portion of what the web has to offer. And my learning in this read was that SSR permits client side JS and refers only to the initial view render.
I'm with you, if this is indeed a trend or a hype of requiring "your site should work even with JS disabled!" then I totally wonder what's the point, because almost no modern app or site works correctly without it.
I develop JS-driven sites all the time, and have no problem visiting other JS-driven sites.
However, I do find it kind of tacky if a site requires JS and there is no content on the site whatsoever (i.e. a completely white or black page), without any noscript tag being used to tell the user to enable it.
Totally understood. I was slightly out of context when I posted it. Good article though.