Re:Performant Front-End Architecture
by scarmig on Tuesday February 11, 2020 @02:06AM
(#22296660)
A SPA is predictive of a web application that has substantial performance, UX, and accessibility issues. A high schooler can build a page with some simple HTML and some jQuery sprinkled in that makes for a substantially more pleasant experience than teams of professional developers regularly manage to do with SPAs. I'm sure there are SPAs that are pleasant and add value above the alternative, but they are clearly very hard to build correctly, as evidenced by how many multi-million dollar SPAs are pieces of shit. It's kind of besides the point whether that's an organizational or engineering failing, because the very fact that SPAs lend themselves to those kinds of failings is an indictment of them.
[ Parent
| on HN ]
The fact that very large SPAs are harder to build and maintain and thus easier to mess up isn’t a very compelling argument for the people who have the ambition to build great SPAs. More ambitious projects are easier to mess up, of course.
Before I was a professional developer, I made a really small application using just HTML, CSS and some jQuery: just a site that listed about ten recipes. When you selected the next recipe, it would change the page's background colour, doing a full repaint in the process. It was terribly slow.