Earlier quoted context omitted.
> one should avoid SPAs like the plague Why? I don't see any basis for such a statement, but I'm more than willing to learn.
SPAs are basically an exploit, taking advantage of a dynamic document model and a language intended to layer a little bit of behaviour atop that model, and using it instead to deliver entire applications. It's a little like noticing that sed is Turing complete, and thus writing a text editor in sed. The Web is supposed to be about resources and links between them; that's what REST is about (in a very real sense, REST…
Browser History (2013)
51–52 of 52 posts
Re: Browser History (2013)
#52Earlier quoted context omitted.
SPAs are basically an exploit, taking advantage of a dynamic document model and a language intended to layer a little bit of behaviour atop that model, and using it instead to deliver entire applications. It's a little like noticing that sed is Turing complete, and thus writing a text editor in sed. The Web is supposed to be about resources and links between them; that's what REST is about (in a very real sense, REST…
You are not giving reasons against SPAs which is what you said earlier, you are giving reasons for using the right tool for the job. Which nobody disagreed with from the beginning, not me anyway.
I think being inefficient ('writing a text editor in sed') and impeding doing things the right way ('it's a lot easier to take a clean REST API and use it from JavaScript than it is to take a purpose-built SPA and try to turn it into a proper REST system') are reasons not to write SPAs, no?
And the presence of reasons to write proper HTML/HTTP apps implies why one shouldn't write improper SPAs, no?