Front-end developers forgot how to store state in the URL. Everyone suffers.

🤣😂😅😂 Actually most newer frontend dev weren’t taught URL fragments and query params It’s all useState these days 😂😇

Devs who don't know teaching devs who then also don't know. It's generational ignorance.

She's stubborn. She's a Gemini. And of course she's spot on about the URL nav. But I take some issue with infinite scroll. It can be buggy to implement, and sometimes it's not worth it, even with IntersectionObserver. I usually advocate for pages or click-to-load when most users will never need additional pages of data.

IMO if devs can't properly do back/forth navigation restoring state, then it's better to _not_ have infinite scroll at all. Most implementations are too user hostile.

The energy here is💯

Inviting her to every design review *immediately*

This such a true statement. URL state is state management on easy mode and a great benefit for users. Imagine queries and pagination without URL state?

@svenasol It's not hard to imagine. It's everywhere! `const [page, setPage] = useState(0)`

I've never used infinite scrolling cause it sucks... URL query params are the way to go for initializing a page with custom params. Maybe beginners were not taught that..

We also have `history.pushState` for SPAs, that no one uses! It's how we built our Pagination component to restore infinite scroll state on back/forward navigation: