4 ms·
Right, totally understand, but, functionally, these are pretty much the same UX (and a pretty common one). My point is that this is quite a bit of code for the
by carsongross 10y ago
Right, totally understand, but, functionally, these are pretty much the same UX (and a pretty common one).
My point is that this is quite a bit of code for the same UI and, unless there is a compelling reason to have a client side model (which, of course, introduces the complexities of syncing w/ a server side model/data store) then you end up with a lot of complexity for very little benefit.
- firasd 10y agoYeah, fair point. I would say, besides interacting with server-side updates, the other use case for something like React is when you have a bunch of event listeners and find they're getting out of control (onclick function triggering something else which has a condition to check the class attribute of something else etc.)