2 ms·
I should have added the caveat that there will always be a handful of cases where you do need absolute top performance. However, I do think that for the vast ma
by rxcfc 12y ago
I should have added the caveat that there will always be a handful of cases where you do need absolute top performance. However, I do think that for the vast majority of apps we'll end up at a point where performance isn't the deciding factor. It doesn't mean that we shouldn't keep improving performance, just that being the fastest doesn't matter so much if all the options are very fast.
- hayksaakian 12y agoit seems like if you're concerned with performance, react vs ember is not the conversation you're having. your concern would be whether to use a framework at all
- poolpool 12y agoOr whether you should even be using a web app.
- rxcfc 12y agoPerformance is a relative term. One could just as well argue that if you're really concerned with performance you should just write machine code.
- hayksaakian 12y agoi suppose i presumed a difference of 2x either way (worse/better) to justify picking one over the other -- given that frameworkless is ultimately the most optimize-able. do you need something to be "at least X(ms) fast" or "faster than what company Y is doing" or "as fast as possible, no exceptions"