2 ms·
I'll just direct you to the first reply on Stackoverflow here: https://stackoverflow.com/questions/453610/javas-virtual-machine-and-clr https://stackoverflo
by Someone1234 12y ago
I'll just direct you to the first reply on Stackoverflow here:
https://stackoverflow.com/questions/453610/javas-virtual-machine-and-clr https://stackoverflow.com/questions/453610/javas-virtual-mac...
- pron 12y agoMost of the things in that answer says are simply irrelevant. - The biggest relevant difference -- which he mentions -- is indeed value types, which are coming to Java, - The CLR doesn't have coroutines. Yield/await are what's known as "stackless coroutines" and are, AFAIK, implemented at the language level (and besides, stackless coroutines are a far cry from coroutines, as the most powerful concept of coroutines is the stack). The JVM, OTOH, offers such sophisticated bytecode manipulation capabilities that full coroutines can be implemented as a library (e.g. Quasar). - What he says of bytecode/package design bears absolutely no relevance to the quality -- or power -- of the VM. Those are just simple design tradeoffs with little effect on results. Also, see my reply to math.