I obviously agree, performance does matter and react isn’t fast enough without tricks. But I would argue that in the case of a graphics editor it may be wise to move outside of the fw, both for perf and scheduling issues.
I say this as someone who has written (and rewritten) an image editor.
I say this as someone who has written (and rewritten) an image editor.
Comments
Some factors are complex to elaborate on in the article.
In React, the data model layer(which contains many classes) and render engine are separated.
I can’t tell how excited I was when I learned we can use runes in class.
It's kind of a "build your core concerns" thing. Like at a certain point, "my interface" becomes a core consideration for your whole program, and nudging some of your core pieces to either side of a framework gets to be a lot of maintenance TCO even if it winds up performant.