earlier replies
Replying to @stilkov
@stilkov Because they make hypermedia-based flows difficult by forcing static routing in client side code.
1
@szymonpobiega Make no mistake, I hate SPAs. But I believe they can be part of a RESTful app if they use a hypermedia format such as HAL.
2
@stilkov you can build SPAs to request hypermedia-rich responses, parse (optionally render) the data/controls. rinse/repeat. @szymonpobiega
1
1
@mamund I fully agree. @SzymonPobiega
1
@stilkov yeah, that reply should have been directed to @SzymonPobiega w/ you as cc. your roca-style.org covers this already, right?
1
@mamund @SzymonPobiega That’s what it’s supposed to do, yes.
2
@stilkov @mamund would love to see an SPA framework use link relations instead of URLs for routers.
1
@stephen_mizell @mamund Why not skip the SPA idea altogether and use the most supported, documented, supported hypermedia format (HTML)?
2
1
@stilkov those two (SPA & HTML-based APIs) are not mutually exclusive. @stephen_mizell
1
@mamund @stilkov pjax or turbolinks can essentially make a SPA for HTML, can't it?
1
Replying to @Stephen_Mizell
@stephen_mizell @mamund Sort of, although I’d argue it’s no longer an SPA if you do that :-)

Jun 4, 2014 · 9:11 PM UTC

1
Replying to @stilkov
@stilkov @mamund haha, maybe so. With pjax, you are always on the same (single) page, just changing a particular element from ajax request.
1
@stephen_mizell @mamund Sure, but it’s entirely possible to follow the link to do a page refresh when JS isn’t available or active.
1
more replies