Writing kernel modules in Haskell [LWN.net]

Writing kernel modules in Haskell

Posted Sep 14, 2009 12:55 UTC (Mon) by nye (guest, #51576)
In reply to: Writing kernel modules in Haskell by flewellyn
Parent article: Writing kernel modules in Haskell

Indeed. Java is perfectly fast enough for long running, non-graphical tasks.

I suspect this is why a lot of Java developers think that the 'Java slowness myth' is complete FUD, whereas users who sit twiddling their thumbs waiting for the JVM to start or some godawful Swing application to draw think those developers must be on crack.

Totally different experiences.

(Log in to post comments)

Writing kernel modules in Haskell

Posted Sep 15, 2009 1:01 UTC (Tue) by mikov (subscriber, #33179) [Link]

Offtopic:

As someone who has the misfortune of running Java applications on 200MHz x86 CPUs, I feel that it is my duty to announce in public: The "Java slowness" is not a myth! It is real :-)

The overabundance of computing power has made everybody lose their objectivity. Nowadays we even have people claiming that JavaScript (!!!) is as fast as C. Similarly, a couple of years ago we had (the same?) people claiming the same for Java. In reality, I am thinking that Java is probably about 10x slower than C, and JavaScript 10x slower than Java :-)

People seem to believe that JITs can offer infinite improvements. In reality I suspect that we will never see a 2x improvement for JavaScript JITs compared to now without changing the language itself.

Java speed arguments

Posted Sep 17, 2009 22:29 UTC (Thu) by smoogen (subscriber, #97) [Link]

It all depends on how the application is written. Many C applications can be quite boggy slow when you make them do the same things that most java bogs down on: graphics, UTF-8, etc.

Look at how slow grep and some other Linux applications got when they started dealing with UTF-8 environments versus good old 'C' environment. Or how slow some applications could be when run in a 'newer' graphical terminal versus say a console or older xterm.

The biggest problem that people run into is that few development groups work on the hardware many users have (though I don't think I have any 200Mhz working systems here anymore myself).