3 ms·
I agree in general, but in the space of UI frameworks it's hard if not impossible to write good cross-framework code. Most frameworks have a specific way of re
by the_duke 10y ago
I agree in general, but in the space of UI frameworks it's hard if not impossible to write good cross-framework code.
Most frameworks have a specific way of rendering the DOM.
In React, manually altering the DOM is an anti-pattern. Even more so if you are using a global store like Redux and/or functional components.
Integrating other "classic" UI code into React is almost always very hackish.
- RodericDay 10y agoComing from PyQt, I just cannot understand or agree with the idea that React is "the future". It's nice for some tasks, sure, but it also feels like a big hack.
- formula1 10y agoIt wont be forever but I think its a fair stepping stone. "set state" I believe is a good alternative to setter/getter and dirty checkers. But react still has some major list issues. Finding the difference between a list of 10,000 items is absurd. This is where I believe React will find its replacement or forced to adapt to.
- hesarenu 10y agoIts very good for most tasks. Makes it simple to create and maintain complex UIs.
- RodericDay 10y agorerender the entire thing "virtually", diff it, then apply the subset of changes that matter? it doesn't seem optimal in any way to me. it's great compared to the alternatives in the browser today, but it seems extremely wasteful compared to an unbound universe of alternatives.
- hesarenu 10y agoWhen in write react code i don't think in terms of diff but in terms of how my ui looks based on current state. Underline implementation can change.