Live data from Hacker News

Traditional JavaScript benchmarks

benediktmeurer.de

21–30 of 43 posts

Re: Traditional JavaScript benchmarks

#21
post #8

Is there a benchmark which tests boring real world usage? The web is littered with people complaining about the performance of dynamically adding rows to tables, especially in IE. The 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...

But that's not the JS implementation - that's the DOM and layout implementation. Faster JS won't improve that.

Re: Traditional JavaScript benchmarks

#22
post #4

"It is probably fair to say that JavaScript is the most important technology these days when it comes to software engineering." Uhh ... no?

+1 "JS is the only API we currently have to use one of the most popular plateform we have" would be more accurate. And it's a terrible API. I can't wait for webassembly.

Could have sworn that webassembly is just a subset of JS.

Re: Traditional JavaScript benchmarks

#23
post #4

Earlier quoted context omitted.

+1 "JS is the only API we currently have to use one of the most popular plateform we have" would be more accurate. And it's a terrible API. I can't wait for webassembly.

Could have sworn that webassembly is just a subset of JS.

You're thinking of ASM.js.

Re: Traditional JavaScript benchmarks

#26
post #20
post #15

I'm going to say something about js benchmarks. Every time you say "Firefox sucks because it's slow" someone will come and say "that is false, look at these js benchmarks! We're in line with other browsers!". But then those benchmarks omit the stuff that actually matters, stuff that Firefox simply sucks at, like DOM manipulation..

http://dromaeo.com/ benchmarks show Firefox beating Chrome for me. What's it missing?

AdBlock

Re: Traditional JavaScript benchmarks

#27
post #20
post #15

I'm going to say something about js benchmarks. Every time you say "Firefox sucks because it's slow" someone will come and say "that is false, look at these js benchmarks! We're in line with other browsers!". But then those benchmarks omit the stuff that actually matters, stuff that Firefox simply sucks at, like DOM manipulation..

http://dromaeo.com/ benchmarks show Firefox beating Chrome for me. What's it missing?

Late edit: I mean the DOM tests specifically http://dromaeo.com/?dom

Re: Traditional JavaScript benchmarks

#29
post #24

"It is probably fair to say that JavaScript is the most important technology these days when it comes to software engineering." Uhh ... no?

Uhh ... yes. It didn't say it's the best, which it probably isn't.

It's maybe fair to say it's the most important technology when it comes to web development. The software engineering world is much bigger than just web development, though.

Re: Traditional JavaScript benchmarks

#30
post #24

Earlier quoted context omitted.

Uhh ... yes. It didn't say it's the best, which it probably isn't.

It's maybe fair to say it's the most important technology when it comes to web development. The software engineering world is much bigger than just web development, though.

JavaScript is important in:

* Web Development is obvious, sure

* Cross platform app development: React Native, NativeScript, Electron, nw.js, and others are extremely powerful, arguably among the best cross platform solutions, and all are gaining in popularity

* Server development. NodeJS is hard to ignore because it's fast, easy to develop in, and has the amazing (if sometimes frustrating) NPM ecosystem.

Software engineering is bigger than that trifecta, but you probably hit the 80% mark if you count all application, web, and server code development. JavaScript is making some inroads into embedded, but it's not as ideal for embedded work, except as a control language from the outside, so I'm not as bullish on JavaScript there.

Throw in TypeScript and a good linter and you have a really strong, flexible, dynamic-yet-statically-typed environment that you can use to hit the (estimated) 80% mark. It really does live at a sweet spot in productivity and software engineering, if you ignore the anti-JavaScript snobs. [1]

[1] Disclaimer: I was an anti-JavaScript snob as recently as about 5 years ago. My background is in games, drivers, C++, assembly language, several other scripting languages, and writing native apps. Things that changed include: 1) Me, in that I gave JavaScript, and later TypeScript a try, 2) I learned to love linters and transpilation, 3) The ecosystem exploded and the tools we have now, including VS Code and build tools like gulp, not to mention the built-in debuggers in every major browser, are now amazing, and 4) JavaScript and TypeScript themselves evolved and upgraded until they were actually both very good languages.

Post reply on HN