3 ms·
I don't have numbers (see https://news.ycombinator.com/item?id=26630618 https://news.ycombinator.com/item?id=26630618 for my speculation). Regarding how I shou
by tracyhenry 6y ago
I don't have numbers (see https://news.ycombinator.com/item?id=26630618 https://news.ycombinator.com/item?id=26630618 for my speculation).
Regarding how I should confirm this is the case, I'd just run a controlled experiment and compare the frame rate produced by the two approaches.
- austincheney 6y agoThis is problematic for two reasons: 1. People make good faith assumptions on performance all the time and those assumptions tend to be either wrong or wildly inaccurately. The most important part of a performance difference is not that something is faster, but by how much faster it is. Without numbers to know the size of difference the conversation becomes meaningless. 2. People, particularly in the context of favorite frameworks and the DOM, regularly speak to performance complete out of context. They believe they are comparing like items when they aren't even remotely related. When it comes to performance there are typically only two things that are measured: execution time on the CPU or human writing time. When it comes to CPU execution time you need to start from the same state and end with an identical product for the comparison to be valid. A comparison between a React component and DOM manipulation aren't comparable enough to buy you that comparison. Its like comparing the production of a hammer factory to the speed of a nail gun.