3 ms·
> 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
by wredcoll 3mo 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...
- wild_egg 3mo agoEvery one of those are things that the browser manages for you if you are using semantic markup and embracing web standards.
- asdfsa32 3mo agoThis is a pipe dream. Browsers have come a long way but they're largely still broken in many many ways.
- wild_egg 3mo agoWould love to hear about which of those listed examples does not currently have native browser support.
- asdfsa32 3mo ago> what the user is currently typing Easy as pie. We don't even have to get into the specific of making things work correctly.
- wild_egg 3mo agoI 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?
- asdfsa32 2mo agoSorry, no. You can not make such assertions yet have little experience with dealing with complex UIs in web. Input management is one of the most difficult aspects of web development once you want anything beyond a simple input. That you have to ask for an example means this conversation isn't going anywhere. Good luck!