Linked by Thom Holwerda on Tue 18th Jul 2006 22:31 UTC, submitted by Tom Magnum
The Mono debate over on the GNOME desktop developer mailing list is heating up again. Philip Van Hoof makes a compelling argument about the need for GNOME decision makers to take into consideration future developers and the over-reliance of C and GObject in GNOME. At what point does a general-purpose, high level framework and runtime become a necessity for GNOME?
Thread beginning with comment 144350
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-06-30
But the problem is if you have lots of applications, made in Python as an example, running in your system then you need memory. Lots of memory. It's the tradeoff: programmers can create better software faster, but you need a powerfull machine. Though we are in 2006; we must look at the future, not the past.
Looking at the future without taking account of the past is very naive... Don't forget that your average user is more likely to use a computer "from the past" rather than the latest dual/quad-core offering with GBs of RAM.
That said, applications using interpreted/evolved languages don't have to be slow and/or memory hungry... Usually, experienced programmers don't have much problem with perceived speed and/or RAM consumption. For instance, they don't open or keep stuff needlessly. They don't let the GC do all the dirty job: they are doing their own part in memory management. They won't choose an O(n^3) algorithm when they know better. In other words, an easy-to-use language won't substitute competence.
Edited 2006-07-19 01:08