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 551451
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: That's terrible
by lucas_maximus on Tue 5th Feb 2013 00:33 UTC 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