4 ms·
This leapt out at me: [Javascript] engines are being overhauled and souped up and tuned and re-tuned to the point that performance is improving by orders of ma
by gruseom 18y ago
This leapt out at me:
[Javascript] engines are being overhauled and souped up and tuned and re-tuned to the point that performance is improving by orders of magnitude. Scanning the DOM tree and doing things to it, which used to be slow and difficult, is becoming lightning-fast and easy.
This is not only a non sequitur, it's false. Making JS faster doesn't imply making DOM manipulation faster: they are two different things. Moreover, DOM manipulation is not becoming "lightning-fast and easy". In some cases it's getting slower and harder. (This is sort of my bête noire right now.)
It may be that Meyer doesn't write applications. That's fine; I don't pay much attention to CSS.
- michaelneale 18y agoyeah I always felt that a lot of the bottlenecks today were DOM related - sure having fast JS means you can do more crunching in JS itself, but at the end of the day the user still experiences the sluggish dom when you are trying to build up a screen.