Well yes, there is the argument that Java.next already exists -and is called C# :-) (or is java.next called android?)
So why exactly is there not a C# compiler for the JVM already (maybe using mono classes for the framework)?? -or is there ?? (there is mainsoft but that is msil to java bytecode) OR.... (and admittedly, this is a stretch -and may have been discussed elsewhere)... Is C# on the JVM what the good Dr Gafter has been hired for?? I know I know -why would they? Well for starters, maybe Microsoft doing it would be better (for Microsoft) than someone else doing it (eg would there be better support for java on the clr if there hadn't been J#??). Ok, its a long shot [ and I already have Dr gafter busy implementing his closures in J# :-) ] Much as I like C#, I would be kind of sorry to see it become the de- facto better java -not so much from the evil empire angle, more that it would feel like globalisation treading on culture. nah -let C# do the hard yards handling manycore, then a real java.next can learn from it like C# learned from java Pete F long bet -one day the jvm and the clr will be considered the same thing --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
