Hacker News new | ask | show | jobs
by wredcoll 1 day ago
> If you have separate state on the client that needs to be managed, you are going to have a bad time regardless of framework.

Yeah, because clients never need to keep track of state like which block is expanded or which tab is selected or that the previous page was or what the user is currently typing...

1 comments

Every one of those are things that the browser manages for you if you are using semantic markup and embracing web standards.
This is a pipe dream. Browsers have come a long way but they're largely still broken in many many ways.
Would love to hear about which of those listed examples does not currently have native browser support.
> what the user is currently typing

Easy as pie. We don't even have to get into the specific of making things work correctly.

I don't understand what is broken with the browser's management of typed content. Do you have an example of UX that requires a custom state management layer on top?