@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
@jon_moore love how you & @stilkov (nitter.vloup.ch/stilkov/status/6…) both focus on the "P" here. is that the real problem? "a page?" @darrel_miller
@mamund @darrel_miller A single page app is retrieved from a single page. It’s like a WS-* “web” service running in the browser.
2
@mamund @jon_moore @darrel_miller To me, it is. It’s giving the application a URI as opposed to giving one to the things living inside.
2
@mamund @jon_moore @darrel_miller I’m totally fine with using JS as a means to extend the browser’s capabilities for certain content.
Jan 12, 2016 · 4:36 PM UTC