On Thursday, 10 January 2013 at 09:05:53 UTC, eles wrote:
On Tuesday, 8 January 2013 at 23:10:01 UTC, Paulo Pinto wrote:
Am 08.01.2013 17:12, schrieb Benjamin Thaut:
Am 08.01.2013 16:46, schrieb H. S. Teoh:
Without dismissing your experience in game development, I
think that your experience was spoiled by D's GC quality.
After all, there are Java VMs driving missiles and ship battle
systems, which have even higher timer requirements.
Yes, but they are relying on specific, very special constructs
of Java, such as:
http://www.rtsj.org/specjavadoc/javax/realtime/NoHeapRealtimeThread.html
http://www.rtsj.org/specjavadoc/javax/realtime/RealtimeThread.html
which have very little, if any, to do do with regular Java.
BTW, since when a Java programmer should be concerned about...
heap? What's that? malloc()?
Any developer worth its salt should worry how their application
makes use of the available resources.
The fact that it uses the same syntax as Java, simply does not
mae it Java, at least in the (regular) JVM sense.
The JVM is just a possible implementation of Java, the language.
It was quite an unfortunate decision for the Sun marketing team
to call the language and the VM the same name.
This always ends up in lots of confusions when people consider
the JVM to be the only way to execute Java.
Usually only developers with compiler design background end up
making the difference, as languages and implementations are quite
two different issues.
--
Paulo
