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 551452
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: That's terrible
by ebasconp on Tue 5th Feb 2013 00:35 UTC in reply to "RE[5]: That's terrible"
ebasconp
Member since:
2006-05-09

Speed is not the only metric when writing applications.


Performance and programmer productivity are the two most important metrics when writing apps.

IMHO Qt provides a good trade-off between both of them: You can write cool and easy-to-write apps in a native language.

Reply Parent Score: 3

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

That's your subjetive opinion, not mine.

Edited 2013-02-05 00:37 UTC

Reply Parent Score: 2

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

Performance and programmer productivity are the two most important metrics when writing apps.


ERRR NO! While both are important I would argue quite strongly that performance isn't as important as it was.

When we have more processor power and RAM than most of us can possibly use. The main bottleneck these days in Desktop applications is I/O (bar a few specialist applications).

I'd rather have something run slower that ran accurately and had a maintainable code base than something that ran fast.

Or have languages that are easy to understand like python (as opposed to JavaScript which I think is much more difficult to understand) and have the same sort of effort that has gone into JavaScript execution optimization in recent years.

Edited 2013-02-05 00:48 UTC

Reply Parent Score: 2

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

Watch this video:

http://channel9.msdn.com/posts/C-and-Beyond-2011-Herb-Sutter-Why-C

I agree with what Herb Sutter says here! ;)

About "maintainable code"; it does not depend on the language but on the programmers, design, etc. I have seen unmaintainable/hard to read/hard to understand Java code and very beautiful C++ code... and viceversa.

Edited 2013-02-05 01:06 UTC

Reply Parent Score: 3