News for hackers. Stuff that matters.
Re:Why Systems Programmers Still Use C (2006) by ajross on Monday March 19, 2012 @12:47AM (#3722362)
It's mostly a semantics thing, but no: most "systems programmers" would not categorize those applications as "systems tasks". They're just apps. By convention, "systems programming" means dealing with the bottom of the abstraction stack. Java code can't make syscalls. Calling conventions for Java methods aren't specified at the level of CPU registers or instructions.

So writing a JVM is systems programming. Writing a Java-based data store is not, even though other stuff then sits on top of the store.

Re:Why Systems Programmers Still Use C (2006) by pjmlp on Monday March 19, 2012 @08:55AM (#3723673)
It is possible to do syscalls in Java.

Following your example there are also JVMs coded in Java.

Re:Why Systems Programmers Still Use C (2006) by ajross on Monday March 19, 2012 @11:25AM (#3724320)
It is certainly not possible to do syscalls in "Java". A system call is a special CPU instruction (e.g. INT, SYSENTER) not accessible to or defined in the Java VM specification.

What you do to effect a syscall is to call a JNI function to do the work. JNI is a C (!) API, defined in terms of the C (!) ABI for the platform.

And sure: you can generate native machine code in Java, just as you can in python or bash or even BASIC. But you can't call it.

Re:Why Systems Programmers Still Use C (2006) by pjmlp on Wednesday March 21, 2012 @06:21AM (#3733752)
Depends what you consider Java, as there are VM extensions coupled with compiler magic that allow it.

One such example is the Jikes VM:

http://jikesrvm.sourceforge.net/apidocs/latest/org/vmmagic/p...

Or the Sun's research in writing drivers in Java http://labs.oracle.com/techrep/2006/abstract-156.html