We always see these performance benchmarks, which are great but are low on the totem pole for technology choice.<p>Really good questions to ask and statements to reassert:<p>* Does is scale well?
* Will this framework / library help me in my career forward?
* How hard is it to implement features?
* Is the framework / library enjoyable to work in?
* Does the framework / library lend itself to allowing elegant solutions?
* Does the framework / library provoke a thoughtful and/or refreshing pattern or style in your code?
* Is the framework / library sometimes blocking solutions to problems?
* Can a new team member readily understand this, explore and contribute after a day or so of training?
* How easy is it collaborating with others?
* This framework / library is simple and understandable enough to get started quickly
* I am intrigued by this framework / library.
* There is a lot of support and resources
* There aren't a lot of grey areas<p>As far as I know, React knocks these out of the park.
Not necessarily addressing the speed portion, but if you're going to give a key to a repeated item in React, it is best to use the index instead of a unique identifier(if the overall DOM structure does not change much between renders) so that React does not destroy and recreate each item on tree change.