Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • On the other hand, BeOS (C++) is still more responsive than my Linux desktop.
    BeOS' responsiveness has nothing to do with its use of C++ as an implementation language. You could reimplement Linux and C++ and it wouldn't magically become more responsive.

    When comparing two systems for speed/scalability, the only thing you can reasonably compare are the design and engineering of those systems. In every case, the better designed/better built system will be faster and more scalable. Period. The language of implementation is irrelevant.

    What the BeOS/Linux comparison highlights is that BeOS is the first OS to be built with a fresh design that assumes it will run on modern hardware architectures, and presumes that it will need to support a GUI and heavy realtime digital media usage. Linux, on the other hand, is a 30+ year old OS design that was created to express a design that is inherently cross platform.

    The Java/C++ comparsions are meaningless because they encompass too many engineering and design decisions all at once -- VM vs. machine code, differences in standard libraries, differences in library models that bleed through into the application, differences in application design philosophies, and low level details such as threading issues and cache coherency. At the end of the day, it's like making a vague generalization from comparing a Ford Explorer against a Volkswagen GTI and trying to infer whether manual or automatic transmissions are "faster".