4 ms·
The benchmarks used for the article was from 2005. Make sure to check out the 2009 versions: http://gmarceau.qc.ca/blog/uploaded_images/size-vs-speed-vs-depand
by tlrobinson 17y ago
The benchmarks used for the article was from 2005. Make sure to check out the 2009 versions:
http://gmarceau.qc.ca/blog/uploaded_images/size-vs-speed-vs-depandability-paradim-2009.png http://gmarceau.qc.ca/blog/uploaded_images/size-vs-speed-vs-...
V8 has propelled JavaScript into the coveted bottom-left corner, which is awesome. SquirrelFish Extreme should be right up there with it, if it were included.
- SwellJoe 17y agoMore reason to believe JavaScript is going to be huge on the server-side. As concise and (nearly as) powerful as Python, Perl, and Ruby, but getting faster at a much more rapid clip...and already required for the front-end, so everybody on the team is already familiar with it. Library coverage will take another couple of years to reach a reasonable level, but I'd bet on it happening.
- kinghajj 17y agoI agree. Once I learned how truly powerful Javascript really is, once you get past the horrible DOM, I knew it could one day become a general-purpose scripting language and not just a web one. As soon as someone makes a good command-line Javascript interpreter, web apps will come as soon as someone creates a CGI extension to that interpreter.
- tlrobinson 17y agoI'm working on it: http://jackjs.org/ http://jackjs.org/ http://narwhaljs.org/ http://narwhaljs.org/ https://wiki.mozilla.org/ServerJS https://wiki.mozilla.org/ServerJS
- silentbicycle 17y agoHave you ever looked at Lua?
- deleted 17y ago[deleted]
- akkartik 17y agoI'm amazed gcc is slower than java. And it's more expressive than scala and f#? Something's gotta be wrong there..
- fauigerzigerk 17y agoYou need to look at how many data points each language implementation actually produces. gcc runs all programs whereas java steady state (the one that looks faster than gcc) lacks a lot of data points (i.e programs). As you can see in the diagram gcc's star is pulled towards the right by one data point (at least it looks like one). If java steady state ran all programs its star might shift to the right as well. Or it might not. It's just not comparable as it is. You need to look at the actual numbers instead of the diagrams. My own benchmarks that I run on our heavily algorithmic long running code consistently show Java about 10% to 20% slower than gcc (C++) and memory usage about twice that of the C++ implementation (excluding the JVM memory itself). C and C++ performance depends heavily on avoiding malloc/new. C/C++ code that gratuitously allocates and frees heap memory tends to be much slower than Java code.
- kingkongrevenge 17y agoA two line fix to compile in something like smartheap typically makes that memory allocation penalty go away. Not that it's hard to avoid unnecessary allocation/deallocation.