9 ms·
This comment touches on some points which don't make sense from an engineering perspective. Different tools for different use cases. You can't throw the baby o
by metalforever 6y ago
This comment touches on some points which don't make sense from an engineering perspective. Different tools for different use cases. You can't throw the baby out with the bathwater and choose SPAs for every single application. They still perform poorly with SEO and people with disabilities that need a screen reader. It's not black and white (good or bad). Also, using Django and Rails are hardly the same as using Perl and CGI.
- arcturus17 6y agoWhat doesn’t make sense from an engineering perspective? I did not say you should build everything as an SPA. I said you still can build in SSR - not once did I say what you should or shouldn’t do. But I agree - some sites are better off as SSR, static sites or what have you. What in my comment made you think that I think otherwise? I also do not think that Django or Rails are remotely similar to CGI sites - what makes you remark that they are hardly the same, when my comment doesn’t suggest the opposite?
- robertoandred 6y agoNothing about SPAs hurts screen readers.
- tatersolid 6y agoThen DOM changing above or close to current position does trip up many accessibility technologies. Most SPA frameworks load all page components async so the page DOM fills in out-of-order. This is a problem even without accessibility tech, the page content bounces all over the place during load by default in many SPAs.