Replying to @stilkov
@stilkov Great article. Unfortunately many people simply won't accept that there 'App' is better served in the classical way, SAP too hip.
Replying to @stilkov
@stilkov @jeppec "Not breaking the browser" takes effort in server side frameworks too. I like the separation of concerns i a SPA vs SS.
1
Replying to @stilkov
@stilkov reminds of a blog post of mine four years ago: tinyurl.com/htxfplq
Replying to @stilkov
@stilkov You imagine worst-case SPA with best case classic. Proper SPA encourages clean URIs, REST APIs, and performance.
Replying to @stilkov
@stilkov @Medium all very true, but add that web-unaware devs with bad server side habbits will make similar mistakes even without spa :)
Replying to @stilkov
@stilkov I'm late to the party. Currently trying to figure out how many times Twitter will let me tap the heart button.
1
Replying to @stilkov
@stilkov an SPA without the issues you mention; react component model makes up for any complexity incurred doing so theintercept.com
Replying to @stilkov
@stilkov can you give examples of the SPAs you are talking about?
Replying to @stilkov
@stilkov That's totally fine for me. I hate it for exactly the given reasons, every single one of them. #thx for the summary.
Replying to @stilkov
@stilkov: “Why I hate your Single Page App” medium.com/@stilkov/why-i-ha…” like the compare of SPA to SOAP ;-)