335 karma · joined March 25, 2009
Yet it is very chilling to read.
The objective reasons for being not as popular I think, that FreeBSD never positioned itself as a desktop system, and many small things (such as how fast it boots) are neglected. Yet, overall simplicity and order is attractive to me; a lo easier to understand internals IMHO.
Modern PC's unfortunately are so complicated...
And do not forget by the way that Ruby is a memory hog.
http://shootout.alioth.debian.org/u32q/benchmark.php?test=al...
I appreciate your choice, but I'd myself do differently.
Another example of performance-sensitive application of compilers is background Java compiler in Eclipse - even for rather small programs it has to be fast. Ruby is 10-100 (actually more than that) times slower than C/Java, So if you optimizer (wriiten in C/Java/Haskell) needs 0.5 second to optimize code, same code will need (by very optimistic measure) 30 sec. Python not much better. Scheme a bit better (especially Stalin compiler), Lisp almost good.
However, if you do not have the target datatype you dealing with during compilation, you are destined to simulate them.
Example: ((unsigned char) 2) + ((unsigned char)255) = 1
That is in C. In ruby you'll have to manually check for overflow, and do it for each operation. You can invent classes all kind of things, but why? Use a language with types, and the check will be done for you by you Core Duo.