3 ms·
The criticism makes no sense to me. jQuery is just there to make things nicer that you'd already be doing. It doesn't need to be an MVC framework.
by jimmaswell 7y ago
The criticism makes no sense to me. jQuery is just there to make things nicer that you'd already be doing. It doesn't need to be an MVC framework.
- benbristow 7y agoFor example, React isn’t an MVC framework. It’s a library. It allows rendering DOM declaratively based upon a state/props. jQuery just changes the DOM. It gets very difficult to keep the DOM in sync with the JavaScript backed data when there’s multiple moving parts.
- lacampbell 7y agojQuery just changes the DOM. It gets very difficult to keep the DOM in sync with the JavaScript backed data when there’s multiple moving parts. Again I don't understand this argument. What's difficult about it? People have been doing it with win forms for well over a decade now.
- dragonwriter 7y ago> Again I don't understand this argument. What's difficult about it? People have been doing it with win forms for well over a decade now. And yet it's recognized as a problem there, too, and one of the more recent solutions is state management libraries inspired by those used in Web apps, e.g., there are fairly direct copies/adaptations of React and Redux for .NET specifically to address this issue.
- gnaritas 7y agoSo don't use javascript backed data; use your ajax calls to fetch new pieces of UI, not data. Keep your data on the server, send chunks of UI to the client rather than json.