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 551424
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: That's terrible
by lucas_maximus on Mon 4th Feb 2013 22:15 UTC in reply to "That's terrible"
lucas_maximus
Member since:
2009-08-18

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

Reply Parent Score: 4

RE[2]: That's terrible
by segedunum on Mon 4th Feb 2013 23:51 in reply to "RE: That's terrible"
segedunum Member since:
2005-07-06

Yes, I do wish they would. Because JavaScript is such a poorly defined language engines like V8 have to use heuristics on it over time. JavaScript didn't suddenly become a world beating language environment because of V8. Those who do code shit like node.js.

Reply Parent Score: 3

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

Depends of what version of are you targering to, if you talk about an old version of javascript then yes, if it is a newer specification like Harmony then no.

Edited 2013-02-05 00:16 UTC

Reply Parent Score: 2

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

It not poorly defined. JavaScript is a proper programming language with a proper language specification.

JavaScript is simply dynamically typed.

There are some oddities that come up thanks to the JavaScript Semi-colon insertion mechanism and the function scope (i.e. Hoisting).

There are some evil things that the programming language allows you to do (some of the more evil things can be effectively disabled with "Use Strict").

JavaScript has a pretty strong community and if you really get your head around it you can do some very neat things that you can't do in other languages easily.

As another has said the newer specifications are pretty good.

As for the viability of things like node.js, Trello and other quite robust web apps that were developed in reckon time pretty much disproves the notion that it is rubbish.

Edited 2013-02-05 00:35 UTC

Reply Parent Score: 3

RE[2]: That's terrible
by ebasconp on Tue 5th Feb 2013 00:21 in reply to "RE: That's terrible"
ebasconp Member since:
2006-05-09

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


The "almost" is the key word here.

As the original poster suggests, why should I (an end user) have to have poor performance (and a lot of resources uselessly being used) because the programmer of my applications did not know how to implement them in some native language?

Edited 2013-02-05 00:24 UTC

Reply Parent Score: 3

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

Why not, javascript is widely use for server side, mobile and desktop applications, and it is faster than Python BTW.

Edited 2013-02-05 00:29 UTC

Reply Parent Score: 3

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

The "almost" is the key word here.

As the original poster suggests, why should I (an end user) have to have poor performance (and a lot of resources uselessly being used) because the programmer of my applications did not know how to implement them in some native language?


Firstly we must have a different definition of "almost".

Secondly these days the main cost of any project is not the hardware, but rather the development costs. Most cheap mobile phones have more memory and processing power than we had a decade ago. I doubt you will even notice it.

Thirdly I expect there is more client side processing on a lot of webpages and applications that you probably aren't aware of.

I been writing a Samsung TV applications. Everything is done via client side processing ... it works fine on a TV's which is running some flavour of Linux and probably has either MIPS or an ARM processor.

Reply Parent Score: 3

RE[2]: That's terrible
by voidlogic on Tue 5th Feb 2013 01:28 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[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