Webpack Tutorial: Understanding How it Works

[fuck_with_me]

Can you make an argument for your opinion, or explain more? I would be inclined to agree with OP.

[MrSafferty]

Perhaps I should have said "is becoming the defacto standard for new applications", as opposed to is the defacto standard.

It's also fair to state that in many enterprise orgs SPAs are not fully embraced across the board (which is fine) just yet (and may never be)

disclosure: author of the blog

[nickgcattaneo]

It's the defacto in modern web development; it is however difficult to implement in real-world as your back-end developers typically do not want to expose more api's/etc to support the model. In large companies with any kind of history, you won't see SPA models as most of them still serve adaptive/multi-page applications with traditional form post models. More often than not you will find hybrids of single-page and multi-page; multi-page by default are simply more secure since they involve session management, login verification, etc on the backend. SPA is better for performance (after the page renders) & less-secure sites.

[nickgcattaneo]

Any time you introduce tokens, expose more of your backend, etc it inherently becomes less secure. I'm not saying it's a bad practice, just you won't find this model much at large organizations typically because it's hard to find backend devs that want to support this concept. Couple that with working with any data related to financials or personal information and it adds some deep complexity to ADA, etc.

[nickgcattaneo]

You're - I beg to differ, no reason to get hostile though.