Replying to @serialseb
@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
@darrel_miller all the browser examples in my new book will be SPAs. @serialseb @beyond_code
4
@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
@mamund @stilkov @darrel_miller Would you really say a browser is a "page" though?
1
@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
Replying to @mamund
@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
@stilkov so none of those letters apply to that problem, right? i can do what you say w/ many pages/apps. @jon_moore @darrel_miller
1
Replying to @mamund
@mamund @jon_moore @darrel_miller Sure thing. You’re definitely not in the SPA mainstream with that approach, though.

Jan 12, 2016 · 4:37 PM UTC

1
Replying to @stilkov
@stilkov could be. would not be the first time, eh?<g> @jon_moore @darrel_miller
2