Sigh. So many things wrong here. This is exactly the kind of article that people take entirely the wrong way
4
1
2
"Don't build an SPA"
No actually do, just don't use a dumb ass framework to do it. It's not rocket sciences and you'll learn a ton!
2
People are already down on SPAs because of people having made terrible ones in the past. We need to move *forward* not back to full reloads
4
1
@beyond_code “full” reloads are not necessarily a problem. One page to do them all is a losing game, it just plain sucks, api first is dead
2
@serialseb Api first could still work in a web browser using Service Worker to intercept. But the Single Page thing should die. @beyond_code
2
@mamund Would you consider building a larger project using that approach?
4
@darrel_miller finally, let's keep in mind that the HTML browser is an "SPA" and has done rather well for the last 25 years.
5
1
@mamund @darrel_miller By what definition? It’s most definitely not an SPA. It’s the very opposite.
1
@stilkov it's a single app for all websites in the world. seems like an SPA to me. we clearly have diff definitions. @darrel_miller
5
@mamund @darrel_miller Most importantly, in my view, it moves way to much logic to the client – the one I’d prefer lived on the server
Jan 12, 2016 · 4:31 PM UTC
1