Mastodon Feed
slightlyoff@toot.cafe ("Alex Russell") wrote:
Does your team need to adopt complex, expensive, and hard to operate JS frameworks for your frontend? A handy guide!
Attachments:
- Should your team adopt React/Angular/etc.? Only if your site needs to be an SPA. (remote)
- Does your site need to be an SPA? Only if data gets updated many times in the same session (either by the user or the server) or in cases where access to underlying hardware is critical to the experience. (remote)
- One helpful way to think about these tradeoffs is through the lens of session depth and data model locality. It only makes sense to move your components to the client if you're also moving your data to the client. And *that* only makes sense if sessions are so long that you can amortize up-front costs based on subsequent use. (remote)
