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 and, as you already pointed out, my small SPAs would not be needed at all if the browser supported other hypermedia formats.
1
@mamund @darrel_miller Sounds as if you’re building a lot of little SPAs. Sort of makes them non-SPAs in my book :-)
2
@stilkov size is part of the SPA definition? @darrel_miller
2
@mamund @darrel_miller To me, yes. Just one for all of an application’s use cases.
Jan 12, 2016 · 4:26 PM UTC