3 ms·
I really like the virtue/vice discussion framing this. You don't see virtue-oriented discussion of topics very often unless it's the accusation of "virtue signa
by pjc50 5y ago
I really like the virtue/vice discussion framing this. You don't see virtue-oriented discussion of topics very often unless it's the accusation of "virtue signalling" being flung around.
> I keep seeing Single-Page-Apps with huge JS files that only, in terms of concrete User Experience (UX) benefits, deliver client-side validation of forms plus analytics. Apps rarely leverage the potential of a Single-Page-App. It’s still just the same ‘click, wait for load’ navigation cycle. Same as the one you get with Multi-Page-Apps. Except buggier and with a much slower initial loading time.
Very true - and also of mobile apps that behave in this way, either because they're using the same SPA technology or are just misconceived.
However:
> The Multi-Page-App forces the team to narrow the scope to a level they can handle. It puts a hard limit on their technological aspirations.
I don't see how this follows at all?
The link to https://doriantaylor.com/agile-as-trauma https://doriantaylor.com/agile-as-trauma is fantastic too, as is the whole "I am Vanity" section. But yes, I also agree with the people here asking what this has to do with SPA vs MPA, because I don't understand the scope argument.
(Frankly I could write a paragraph response to each section as if it were a separate blog post, that's how much good content there is here)
- bulatb 5y agoI think he's implying that traditional MPAs are relatively well-understood. The team will pretty much know how to make them and will not expect to break new ground on architecture, discover new things the model enables, or spend a lot of time on "How do we build applications?" versus just delivering on business goals. SPA development is less mature, so there's a lot more room (and sometimes need, or just temptation) to reinvent things.
- throwaway284534 5y agoMaybe I’m just full of Ruby on Rails induced trauma, but I can’t remember any particular pleasant memories. Every app would start with a reasonable and straightforward view layer, usually ERB templates sprinkled with jQuery, and then slowly but surely be consumed by one-off JavaScript snippets. “We need a sortable table on this route and it should support pagination without a reload, but the pagination needs to be persisted to the address bar for outside link sharing.” This feature alone can introduce all kinds of unmanaged state and be a testing nightmare. And if another part of the site uses the same functionality, you’ve just signed up for an lifetime of maintenance, usually somewhere between your server-side templates, and your asset pipeline. God help you if your bugs can be described as, “I have some local state here, but I’m not sure how to get it either up or down to the right place.” Personally, these kind of code smells demoralize me enough to consider a job elsewhere, preferably at a company that uses something like React where there’s bound to be complexity, but at least there’s component boundaries to keep your mental facilities from being overrun by a “simple multi page architecture.”
- pjc50 5y ago> “We need a sortable table on this route and it should support pagination without a reload, but the pagination needs to be persisted to the address bar for outside link sharing.” How would you do that differently in a SPA? Or would that just preclude the link sharing, removing the requirement altogether? Are SPAs doing client-side pagination or something?
- shadowgovt 5y agoI've seen a variety of solutions used in SPAs, from a thin wrapper around server-side pagination to some extremely fancy client mirroring of server state where the client builds an increasingly larger cache of the data coming from the server, complete with eviction strategies and maximum memory usage limitations, and only has to send a request to server side when it knows it cannot satisfy the client's viewing desires with what it's gathered so far.
- bcrosby95 5y agoMPAs are naturally limiting compared to an SPA. And dev teams know this. So does management. SPAs are magical pixie dust that lets you easily code a native experience in the web. Some management thinks this. So do under-experienced dev teams. MPAs provide natural pushback against unrealistic demands and feature requests that your experience might not let you recognize, or that company politics won't let you do.
- onemoresoop 5y agoMy overall experience with SPAs as a user of different services is not so great on average. There are a few services where this works out great but for the most majority it makes the experience worse.
- ellyagg 5y ago> I’ve written in the past about how conferences are the business equivalent of morality plays. They don’t exist to educate or enlighten but to unify a community around shared values—which is why they are great for networking. That is why they need a liturgical adversary; somebody who can represent the opposing heterodoxy. >> unless it's the accusation of "virtue signalling" being flung around. You can't have one without the other.
- rk06 5y agoThe author is talking in context of Frontend system i.e. javascript only. In SPA, a single app consists of all your frontend system. hence has a high scope. While in MPA mode, js is split across multiple pages, and each page has a narrow scope for the javascript code to function. Hence MPA will limit power and misuse of javascript