3 ms·

I think what happened is that the developers that figuratively jumped up and down screaming about compile times all shifted towards interpreted languages. JS h

I think what happened is that the developers that figuratively jumped up and down screaming about compile times all shifted towards interpreted languages. JS has been able to do roughly what C did in the 1990's, in terms of raw performance, for some time now. The folks that need typechecking can pick up Typescript or Haxe or whatever else is attractive. It's the bottom of the stack that really suffers - all the folks that want to work on stuff touching I/O and low level resources directly - and that is hardest to justify investing in. Unix and its baggage remain "untouchable", as these things go, and there are only some hints of promising developments otherwise.

Koshkin 7y ago
> JS has been able to do roughly what C did in the 1990's Basically, what you are saying is that JS slows modern computers down to the speed comparable to 90's computers.
- sigzero 7y ago
  True story.
- lioeters 7y ago
  I laughed, but really, the V8 JavaScript engine has come leaps and bounds in terms of performance. I recall a benchmark that found JS about 25% slower than C++, but 20% faster than Java. (citation needed)
  - hackingthenews 7y ago
    That really depends on what was benchmarked, so much so that dropping random benchmark results is meaningless. A benchmark like this [1] (showing c++ < js < java) is absolutely useless as the person writing it has no idea what they are doing, e.g. using vector in java. Looking at most benchmarks java beats js more often than not, but they are often neck in neck.[2] C++ always beats both, often by a huge margin (when written well).[3] [1] https://www.linkedin.com/pulse/algorithmic-performance-comparison-c-javascript-java-malyshev https://www.linkedin.com/pulse/algorithmic-performance-compa... [2] https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/javascript.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... [3] https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/node-gpp.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
    - lioeters 7y ago
      Thank you for setting the record straight(er), I appreciated looking at some real benchmarks. The one for k-nucleotide looked like it pushed JS the hardest for some reason. Interesting to compare how different languages fare: https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/knucleotide.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... In this one, Java was 2.3x slower than C++, and Node.js 6.6x. Oof, I concede. "JS has been able to do roughly what C did in the 1990's."
pjmlp 7y ago
Nope, we moved into Java and .NET stacks.

Koshkin 7y ago

> JS has been able to do roughly what C did in the 1990's Basically, what you are saying is that JS slows modern computers down to the speed comparable to 90's computers.

sigzero 7y ago
True story.
lioeters 7y ago
I laughed, but really, the V8 JavaScript engine has come leaps and bounds in terms of performance. I recall a benchmark that found JS about 25% slower than C++, but 20% faster than Java. (citation needed)
- hackingthenews 7y ago
  That really depends on what was benchmarked, so much so that dropping random benchmark results is meaningless. A benchmark like this [1] (showing c++ < js < java) is absolutely useless as the person writing it has no idea what they are doing, e.g. using vector in java. Looking at most benchmarks java beats js more often than not, but they are often neck in neck.[2] C++ always beats both, often by a huge margin (when written well).[3] [1] https://www.linkedin.com/pulse/algorithmic-performance-comparison-c-javascript-java-malyshev https://www.linkedin.com/pulse/algorithmic-performance-compa... [2] https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/javascript.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... [3] https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/node-gpp.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
  - lioeters 7y ago
    Thank you for setting the record straight(er), I appreciated looking at some real benchmarks. The one for k-nucleotide looked like it pushed JS the hardest for some reason. Interesting to compare how different languages fare: https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/knucleotide.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... In this one, Java was 2.3x slower than C++, and Node.js 6.6x. Oof, I concede. "JS has been able to do roughly what C did in the 1990's."

pjmlp 7y ago

Nope, we moved into Java and .NET stacks.