We've been lied to: JavaScript is fast
jyelewis.com
We've been lied to: JavaScript is fast
1–10 of 86 posts
Re: We've been lied to: JavaScript is fast
#2I remember node.js benchmarks in the front page of hn showing it to be as fast as hotspot jvm. And this was pre 2012.
And since node is single threaded, you had to run n.cores instances of your app.
For the longest time as a kid what I was lied to was that Java was much slower than Ruby/Python and my perception was painted by the startup times.
Re: We've been lied to: JavaScript is fast
#3Re: We've been lied to: JavaScript is fast
#4Re: We've been lied to: JavaScript is fast
#5Re: We've been lied to: JavaScript is fast
#6There are many things to consider in addition to just JS, like bloated frameworks, dependency hell, startup times... yeah a single benchmark may not show much difference, but when you consider everything else there is a noticeable difference between a JavaScript CLI app and Go/C CLI app.. I can visibly even see a difference for CLI, but my process manager clearly shows any desktop GUI use for JavaScript is severely l…
I think desktop GUI apps also have browser rendering engines chewing resources.
Re: We've been lied to: JavaScript is fast
#7Yes but. https://dev.to/jaredcwhite/the-shocking-immaturity-of-javasc...
All languages have their pain points, and modern JS/TS, while undisputably having their quirks, aren't particularly more quirky than JS (IMHO)
Re: We've been lied to: JavaScript is fast
#8I am curious why this did not happen or what optimization flags were passed in.
If it was prevented optimization through flags, is this a fair test?
Re: We've been lied to: JavaScript is fast
#9In the past when I have written basic benchmarking code like the first example, the compiler will typically optimize all the code away. I am curious why this did not happen or what optimization flags were passed in. If it was prevented optimization through flags, is this a fair test?