3 ms·

The problem was choosing an SPA

• jiggawatts 4y ago
  Precisely. There was someone here bemoaning how difficult it was to follow generic advice of using profilers to optimise hotspots in the application code. He started off with something like: "Why don't you try your 'simple' techniques in a tangled web of hundreds of microservices written in different languages and running on different platforms?" It's like some people can't see the forest for the trees. In the last few years, I've come across about half a dozen existing web sites with hideous performance problems, all of which should have been vanilla HTML but were written as Angular monstrosities. The same teams -- against repeated advice -- have started new Angular projects for sites showing static data, anonymously, to the general public. They start off conversations with "We'll need a web app, an API app, a mid-tier, a service bus, and then this, and then that..." It's madness.
  • danielvaughn 4y ago
    Choosing a framework for that is bad enough, but you could make the case depending on how complex the rendering is. Still…to go with Angular sounds like the literal worst choice. Like at least React is just a UI library and can just be used server side.
    • belmont_sup 4y ago
      That group there…really liked to waste time.
• P5fRxh5kUvp2th 4y ago
  I was looking for this response because I was going to post it if I didn't find it. So many people don't get that their design decisions have consequences and using a SPA is absolutely a design decision.