3 ms·
So you now need a framework to accomplish something browsers have been able to do natively for multiple decades. And we're calling that progress.
by dolni 4y ago
So you now need a framework to accomplish something browsers have been able to do natively for multiple decades. And we're calling that progress.
- pram 4y agowindow.history is from the HTML 5 spec from 2011. It’s as native as anything else.
- acdha 4y agoThe API is mature but usage is not. I still see cases where companies screwed up state management on at least weekly basis so clearly the SPA-building community is still lagging behind where the server-side world was three decades ago.
- berkle4455 4y agoJust wait til you learn about SSR
- rektide 4y agoFor real. The solution to bad url routing in SPAs is distributing our work across a madcap wild ass front-end/back-end split with ill defined borders & no protocols? What's happening now is 500% more complicated. But the magic is well packaged & available by default. The SSR world has frameworks: but as another commenter pointed out, React stopped at being merely a library. And so it's been anarchy, deciding how to SPA, with many folks not realizing how many needs/libraries they really needed to have. I'm hugely in favor of SPAs, but there's been a lack of well-integrated sensible approaches. The attempt to identify & only solve a narrow window of concerns has hurt our ability to imagine what apps are, left huge voids all over.