For one thing, JavaScript engines don't get the luxury (like other language compilers) of having plenty of time to optimize, because JavaScript compilation doesn't happen in a build step ahead of time, as with other languages.
If you want to change selection, open document below and click on "Move attachment"
You-Dont-Know-JS/ch1.md at master · getify/You-Dont-Know-JS · GitHubn, including collapsing redundant elements, etc. So, I'm painting only with broad strokes here. But I think you'll see shortly why these details we do cover, even at a high level, are relevant. <span>For one thing, JavaScript engines don't get the luxury (like other language compilers) of having plenty of time to optimize, because JavaScript compilation doesn't happen in a build step ahead of time, as with other languages. For JavaScript, the compilation that occurs happens, in many cases, mere microseconds (or less!) before the code is executed. To ensure the fastest performance, JS engines use all kinds Summary
status | not read | | reprioritisations | |
---|
last reprioritisation on | | | suggested re-reading day | |
---|
started reading on | | | finished reading on | |
---|
Details