"About half a year ago I was looking around me and seeing stagnation in the GNOME community. I was concerned that GNOME had lost its momentum and that we were just making boring incremental releases that added very little new functionality. I think I was very wrong. I'd like to take this time to list some things that are happening right now in the GNOME community that have me very excited. These are the projects that are actively improving the future of the GNOME desktop." Let's hope a punctuation checker will be part of GNOME too. One Aaron is enough.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-10-13
I know exactly what the differences are between GCC and mono. And mono does execute native code at the end, the VM has a backend that spits out native code to run on your machine, just like the Java vm does. The difference is that it is compiled at run time rather than ahead of time, which means that any optimizations made have to be done more quickly, but also allows for some new optimizations not available on statically compiled code. That's also why it is compiled down to a psuedo-assembly language rather than plain C code, because the final compilation step is much faster.
Edited 2007-08-08 00:04
Member since:2007-07-20
yep, Im familiar with JIT, however mono and java just dont run as fast as standard compiled code.
http://www.mobydisk.com/softdev/techinfo/speedtest/index.html
Edited 2007-08-08 00:34
Member since:
2007-07-20
GCC and mono are different beasts. GCC compiles native code where as mono/java dont - Vala will be compiled C code with no odd runtime dependencies like java and mono.
Vala seems roughly comparable shedskin* or GCC's java compiler - GCJ, which compiles binaries but youll find its not used by many projects compared to sun's java.
* shedskin is python -> C++
http://sourceforge.net/projects/shedskin/