The weight is killing innovations in `JS` frameworks

[ClassicOldSong]

In short, the weight put JavaScript frameworks in an unfair competition.

If this benchmark is called "web-framework-benchmark", I would have no objection on this weight, but... it's called "js-framework-benchmark" so...

The newly added weight encourage frameworks change into "compile time optimizations" that work only in browsers - frameworks who use innerHTML and cloneNode to gain speed in node creation, but only in browsers, while originally JS frameworks can have a much wider availability in multiple other scenarios such as iOS and Android app development(e.g. with NativeScript with DOMiNATIVE), and even embedded GUI development(what I'm working on right now), but these environments are very unlikely to provide a built-in XML parser and even if, won't benefit much from doing so. While document.createElement can be provided and translated very well in multiple GUI implementations, using the same API also provides an even ground for each frameworks to compete about their "JS" part - innerHTML and cloneNode are provided by browsers, not JS itself.

Also, in my opinion, node creation speed isn't that important that needs a ~60% weight, but content updating speed affects user experience in a bigger aspect.

ref: #1341 #1233