Traditional JavaScript benchmarks
benediktmeurer.de
Traditional JavaScript benchmarks
1–10 of 43 posts
Re: Traditional JavaScript benchmarks
#2Uhh ... no?
Re: Traditional JavaScript benchmarks
#3For the context, from the "about" page of the author, he:
"joined Google to work on the V8 JavaScript Engine in the Munich office, where" he's "currently working as tech lead for the JavaScript execution optimization team."
Re: Traditional JavaScript benchmarks
#4"It is probably fair to say that JavaScript is the most important technology these days when it comes to software engineering." Uhh ... no?
Re: Traditional JavaScript benchmarks
#5Re: Traditional JavaScript benchmarks
#6Unless you work in the embeded systems I don't expect people to have done or needed the % 2048 trick.
Re: Traditional JavaScript benchmarks
#7All of these changes that the author is making are changes that the compiler should be generating. Unless you work in the embeded systems I don't expect people to have done or needed the % 2048 trick.
Re: Traditional JavaScript benchmarks
#8The good news is that the next version of Edge 15 has some really good DOM performance improvements.
https://developer.microsoft.com/en-us/microsoft-edge/platfor...