You can use arrow keys to navigate in the map.
I use React for reasons other than performance differences I probably won't notice (I feel it performs very well). I find it a very straight-forward and pleasant framework to work with, it dramatically speeds up my work flow and I choose to use it over anything else I've tried so far.
Its power stems from its simplicity and focus. It solves all the problems with rerendering DOM (event handlers?) but avoids imposing non-essential things, like MVC. The fact that it's even compared to MVC Frameworks indicates that you're probably better off without one.
depending on complexity not everyone needs a strong decoupled uni directional component based render architecture.
React and its components everywhere approach ends up like a piece of program which is more complicated and cluttered than html templates for web designers to think visually on.
React automatically manages UI updates, but this is only true if your UI is extremely basic. React becomes counterproductive when developing apps that aren't mere demos. You inevitably end up having to research how to do basic HTML, CSS and JS all over again within React and its bloated ecosystem.
It's marketed to developers by billion dollar Facebook, a company historically intent on squashing startups.
First, you provide no evidence for their historical intent, and second, the even if they did have a history of intentionally "squashing startups" (whatever that means), I fail to see how that applies to a virtual DOM technology. williamcotton
The argument vaguely suggests that React is a tool that Facebook employs to ruin startups, with no evidence and no connection to whether React is hype or useful. skuro
The benefits of using a virtual DOM over the actual DOM are theoretical at best. The problems that React supposedly solves are theoretical at best.
It solves problems you'll never encounter because you don't have Facebook scale.
Stop comparing React with MVC or any kind of Architecture/Design Pattern and Uni-Directional dataflow. That's completely an invalid point. That's not what React is.
"All problems in computer science can be solved by another level of indirection"
Once JSX is used to render a tree of nodes on the server, it is then necessary to walk the entire tree to serialize it to HTML for sending to the browser. Building and traversing a tree requires more memory and CPU than just running a program that renders (complex) HTML in a single pass.
React brought a fresh idea back to UI software design: If something changes in the model, redraw everything. Don't observe and update specific things as we do in traditional MVC. This is a crazy idea, will this be fast enough? Turns out, it's good enough for most things when using a Virtual DOM.