Linked by Thom Holwerda on Mon 4th Feb 2013 18:41 UTC
Gnome "At the GNOME Developer Experience Hackfest in Brussels, the GNOME developer community has tackled the problem of specifying a canonical development language for writing applications for the GNOME desktop. According to a blog post by Collabora engineer and GNOME developer Travis Reitter, members of the GNOME team are often asked what tools should be used when writing an application for the desktop environment and, up until now, there has been no definitive answer. The team has now apparently decided to standardise on JavaScript for user-facing applications while still recommending C as the language to write system libraries in." Discuss.
Thread beginning with comment 551465
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: That's terrible
by voidlogic on Tue 5th Feb 2013 01:28 UTC in reply to "RE: That's terrible"
voidlogic
Member since:
2005-09-03

"JS VMs are almost as fast as compiled code these days. I wish people would fact check this stuff."

That is a fantasy:
http://benchmarksgame.alioth.debian.org/u32/which-programs-are-fast...

Also you will find most small JS applications spend a lot of time executing library functions written in C and as the application has more and more actual Javascript, performance really degrades. This degradation is both execution speed and memory usage.

Reply Parent Score: 3

RE[3]: That's terrible
by Hiev on Tue 5th Feb 2013 02:07 in reply to "RE[2]: That's terrible"
Hiev Member since:
2005-09-27

What is really surprising is in that link it shows how the Go programing languaje that is suposed to be native is slower than javascript.

Reply Parent Score: 2

RE[4]: That's terrible
by voidlogic on Tue 5th Feb 2013 05:11 in reply to "RE[3]: That's terrible"
voidlogic Member since:
2005-09-03

If you are talking about a large codebase with significant portions of execution time are in the application itself rather than the libraries used (which in nodes case are C), this is definitely not the case. I have ported node.js applications to Go and it was well worth it.

Also, keep in mind this is a single threaded test, Go scales much better on multiprocessor machines than V8 javascript.

(Also the version of Go used is 1.0.3 rather than tip. I switched to tip for a project yesterday and it had a surprising but appreciated 50% speed-up.)

Edited 2013-02-05 05:13 UTC

Reply Parent Score: 5

RE[3]: That's terrible
by Kitty on Tue 5th Feb 2013 06:33 in reply to "RE[2]: That's terrible"
Kitty Member since:
2005-10-01

Include Python in that chart - as the high level dynamic glue language JavaScript is meant to replace in Gnome application development - and JS will indeed look in the same ballpark as C.
C to JS a factor 3.5, JS to Python a factor> 15
Plus, I expect the tooling and engines for JS to grow faster than those for Python

Reply Parent Score: 3

RE[3]: That's terrible
by lucas_maximus on Tue 5th Feb 2013 09:26 in reply to "RE[2]: That's terrible"
lucas_maximus Member since:
2009-08-18

Depends what the code is compiled to doesn't it?

There is native and there is byte code. I meant the latter. V8 performance doesn't stack up bad against Mono and Java for something that is JIT compiled.

Edited 2013-02-05 09:33 UTC

Reply Parent Score: 3

RE[4]: That's terrible
by moondevil on Tue 5th Feb 2013 10:06 in reply to "RE[3]: That's terrible"
moondevil Member since:
2005-07-08

Would like to see how it measures against native compilers for .NET/Java.

Reply Parent Score: 2