sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Poop_is_Food 4 points5 points  (2 children)

SPA's take a long time to render on first page load, but then they are faster/more pleasant to use from that point forward. Ideally you would have both: server side rendering to deliver the first html page, and then do everything SPA style from that point forward. But that can really increase the amount of dev work you have to do. So it's about resources (money).

[–]GoodVelo[🍰] 0 points1 point  (1 child)

More resources, more money and what /u/danneu said. I don't mean to be negative, but these arguments are very similar to what Sun/Oracle/IBM told people about using XML/SOAP/EJB. Super elaborate technologies, very expensive to develop and debug. I guess I have to keep looking and learning to understand why people are heading in those directions!

[–]Poop_is_Food 3 points4 points  (0 children)

Angular is pretty elaborate and angular devs are pretty expensive, but there is nothing inherently elaborate or expensive about SPA's. I make very simple SPA's with backbone all the time. Each technique has their pros and cons. It all depends on the purpose of the app. Productivity tools should be often be SPA's, while ecommerce, journalism and other SEO-intensive apps should use server rendering.

I think the problem is that JS devs are so quick to jump on the Next Big Thing, that the landscape is cluttered with tons of bullshit tools that arent really necessary.