JS web frameworks benchmark – Round 7 • Hacker News Board

krausest wrote: post #4

Udik wrote: post #3

Can someone explain what is "keyed" Vanilla-JS?

Is your question what is keyed (answered in the blog) or what‘s vanillajs (javascript without a framework)?

What is "keyed Vanilla-js". As I understand the definition of keyed, it's a feature that js doesn't have.

EDIT: from the blog:

"All modern frameworks have some kind of binding between data and DOM nodes. This binding is especially interesting when data consists not of a single item, but of a list of items. If data changes the question is which DOM nodes should be updated, inserted or removed."

It's unclear because it seems to talk about data binding (which is not part of js), but actually is talking about an identity association between a DOM node and a data object. I guess it just means there is a one-one association between nodes and data points, and when a data point [identity] changes, the corresponding DOM node is entirely destroyed and recreated.

Re: JS web frameworks benchmark – Round 7

#6

Post by shove » Tue, Nov 21, 2017, 12:31 PM UTC

The download, parse, and startup time isn’t considered, so while this excellently captures runtime performance metrics, it’s not the whole story. Does your app replace thousands of rows in a table?

And yes, I’m questioning the time I spent getting Preact to work rather than going with the React herd. :)

Re: JS web frameworks benchmark – Round 7

#7

Post by krausest » Tue, Nov 21, 2017, 2:49 PM UTC

shove wrote: post #6

The download, parse, and startup time isn’t considered, so while this excellently captures runtime performance metrics, it’s not the whole story. Does your app replace thousands of rows in a table? And yes, I’m questioning the time I spent getting Preact to work rather than going with the React herd. :)

The startup benchmark tries to capture that, but doesn‘t simulate network performance. Still I think it shows some interesting results.