java isn't supposed to be C++. the whole point of java is "write once, run anywhere". compiling to native code does not advance that. just-in-time compilation does.
it only measures in two axes, and has no rotational sensors, so even if it had the precision of a real INS, it would be useless for navigation. it can't tell if you turn or climb.
of course, java has its own problems to work around. how do you handle 'instantiation is allocation', i.e., having the constructor of a stack-allocated object grab a resource, and the destructor deallocate it when it goes out of scope? routine in C++, impossible in Java, but highly desirable nonetheless.
Slashdot Mirror
java isn't supposed to be C++.
the whole point of java is "write once, run anywhere".
compiling to native code does not advance that.
just-in-time compilation does.
it only measures in two axes, and has no rotational sensors, so even if it had the precision of a real INS, it would be useless for navigation. it can't tell if you turn or climb.
of course, java has its own problems to work around.
how do you handle 'instantiation is allocation', i.e., having the constructor of a stack-allocated
object grab a resource, and the destructor deallocate it when it goes out of scope?
routine in C++, impossible in Java, but highly desirable nonetheless.