6 ms·
For anyone deciding whether to read, I'd say the article is broadly centered on this: > As developers, we need to operate under the assumption that good manage
by bulatb 5y ago
For anyone deciding whether to read, I'd say the article is broadly centered on this:
> As developers, we need to operate under the assumption that good management is the exception, not the norm. Multi-Page-Apps and hybrid frameworks let under-resourced, mismanaged developer teams deliver reliable and safe code. That should not be dismissed lightly.
There's also a helpful "Summary" section at the bottom. Overall it frames the SPA vs. TWA[0] debate in terms of which approach is likelier to produce successful software... or successfully produce software, at least.
[0] Traditional Web Application? Do we call it that?
- SilasX 5y ago<deleting because comment was based on a misreading>
- mwcampbell 5y agoCan you elaborate on what you found laughable? I thought the article made valid points.
- hirsin 5y agoWe've largely broken app architectures in AAD down to spa, hybrid, and "webapp". Where webapp means "a server owns the state, and creates a web page and sends it to your browser". MPA is rough - 110% some engineer within minutes of that doc going live will point out that their spa has multiple pages. Personally, I like TWA - will start using that locally to see how it goes. Look for a doc update near you soon...
- resignThis2021 5y agoAAD?
- easton 5y agoAzure Active Directory -- the OP is a PM for that at Microsoft.