4 ms·
To state the obvious: the JS performance advices this person gives won't necessarily apply the same to ALL JS engines. I wonder which specific browser and versi
by hackermom 16y ago
To state the obvious: the JS performance advices this person gives won't necessarily apply the same to ALL JS engines. I wonder which specific browser and version he/she bases the advice on.
(Why the heck do the kindergarten people of HN downvote this? It's a perfectly sensible question.)
- daleharvey 16y agoVery very few of these arent applicable to all javascript engines, most are a by product of the language itself. the only one that is specifically says "yes for ie"
- nixy 16y agoYou are correct. I work with JS engine implementations most people have never heard of. Performance is different between engine implementations, and so is availability of different ways of solving a task. Using the common browsers' best practice for performance doesn't always work for me. My favorite JS engine is the one implemented in the Evo browser. Among other things, it lacks support for arrays and for loops which makes development a tad interesting. And then we have the iPanel browser built for the Sunniwell set-top-box, in which you have no try/catch. Also, if you use more than five chained if/else, the browser will crash. However, this could be viewed as enforcing general programming best practices :)
- cema 16y agoQuote: it lacks support for arrays and for loops Wow. They still call it Javascript? Could you please point at the docs, to see what kind of language they offer? Thanks!