Java is not the best language for system programming. Java has an
interface (JNI) to C. So what one can do is to do the real system work
in C, and call the C functions from Java. You loose platform
independence and have to deal with two languages and the JNI mechanism.

/Thomas

More than somewhat. Great language for writing compilers and assemblers
and linkers, and these were systems software when I went to school ...
If you mean device drivers and O/S components, no, because you can't
address physical memory or registers.

I agree that a systems language needs to be able to do arithmetic and
turn the result into a pointer. That is needed for both memory
management and hardware register addressing.

It may also need to be able to turn a pointer into an integer type.

However, I don't think it needs to be done "like C". It could be
isolated in a special API, so that e.g. coding reviews could look for
over-use.

Patricia

Java is very well suited for databases and application servers.

IBM has shown that most of a JVM itself can be written in Java.

MS has shown that most of an OS can be written in C# and
that should indicate that Java could be used as well.

A few things can not be written in Java, but the lines
of code would be relative small compared to the
total size.

Arne

It depends on the architecture, doesn't it? There are hardware
implementations of the Java processor; they run Java down on the metal and
you can't get lower level than that. The Intel x86 architecture is not
designed to run Java on the metal, and Java is not designed to compile
down to x86 native code. However, there are compilers (including GCC)
which will compile Java to x86.

You'd almost certainly need a Java aware BIOS which appeared as an instance
of a custom class; and you'd probably have to write that BIOS in assembler
or possibly C. But the BIOS could be very small indeed.