JS Performance Debate
The cluster centers on debates about JavaScript's performance compared to native or compiled languages like C++, Rust, and Go, including discussions on JIT compilation, memory usage, and suitability for high-performance tasks.
Activity Over Time
Top Contributors
Keywords
Sample Comments
In my experience JS is not as fast as compiled languages.
I would be surprised and worried if a native tool would be slower than a javascript one, even with JIT, wich is useless for short lived programs
Nowadays JS is as fast as C++, if not faster.
Maybe a naive question but did you consider writing it in language that is typically faster (C++/Go/Rust)? I understand the many benefits of it being written in JS but there is an inherent maximum level of performance that JS can achieve in certain workloads.
it would probably still be fast enough, the difference between JS perf and native perf is surprisingly slim.
JS is still slower than native code, and has worse memory consumption.
You'll never get faster code out of JS, though. Language design matters a lot.
Javascript is not usable, you wont be able to make anything useful if that is your underlying VM.You need fast turnaround AND performance at the same time.You are sinking your cost into a dead-end proving the articles point.
Javascript runtimes these days are plenty fast. You can definitely have a snappy editor and in only rare cases might need C. The issue is probably reducing the browser overhead, i.e. rendering DOM updates and the memory weight of the entire browser stack, etc.
Is Javascript significantly slower? It is extremely common in the real world and so a lot of effort has gone into optimizing it - v8 is very good. Yes C and Rust enable more optimizations: they will be slightly faster, but javascript has had a lot of effort put into making it run fast.