26 ms·
I've just started using it on a fairly simple project so I only have first impressions. But it seems like for a UI that's not too complex it could be a big time
by cageface 5y ago
I've just started using it on a fairly simple project so I only have first impressions. But it seems like for a UI that's not too complex it could be a big timesaver. I need to spend more time with it before I can decide where I'd draw the line and switch to a full blown SPA but it definitely expands the class of apps you can build without much JS.
- DanielKehoe 5y agoState management on the front end? Is that the differentiator that forces the need for a full SPA framework? Anything else that can't be done purely with web components?
- cageface 5y agoI'm sure there are people much better qualified to answer this than me but it feels like there would be a point at which trying to manage a very complex UI with all these little HTML fragments over the wire would get unmanageable. I'm just guessing though. So far I haven't done anything that complex with it. I guess I'd also miss having Typescript for a UI with a lot of components. You can do some client-side state management with Stimulus though.
- bryanrasmussen 5y agoI think the only state management that really requires SPA is of course the state between pages. But why actually have pages - I actually think this is a good differentiator of if your site is naturally an SPA or not - if you really need pages, perhaps because people need to be able to bookmark a specific part of your site that is more important to them than other parts - your site as a whole might not actually need to be an SPA although it might have parts of it that function as SPAs.