3 ms·
I was going to say the same thing you said. Angular/React routing, if done correctly, don't have those problems at all. If you let the SPA framework do your pag
by craig1f 9y ago
I was going to say the same thing you said. Angular/React routing, if done correctly, don't have those problems at all. If you let the SPA framework do your page-changing for you, open-in-tab and history still works. If you do amateur stuff like, you bind a button to a function, and the function does an document.location.href update, then you're going to have some weirdness.
My biggest problem with SPA the last time I did it (a year ago) was optimizing it for search engine crawling.
- amsheehan 9y agoGoogle's crawler at some point last year started indexing a really large mostly text based AngularJS app I built: https://www.fwdeveryone.com https://www.fwdeveryone.com Even if it didn't, headless chrome makes it really easy to pre-render content for web crawlers.