Their "interoperability" doesn't even extend as far as making .Net portable. So when my Java app swans from Windows to Linux to OS X with nary a code change, will .Net follow it and still be interoperable?

Will it friggin' buggery!

So why bother with .Net in the first place?

...Stalin promises to recreate a free and liberated Poland once the war is over.

More Lies, More Bullshit - more movers to Linux.

Dan'l Lewin, corporate vice president for strategic and emerging business development, told what's looking like the last JavaOne that Microsoft's "intent and ongoing commitment" is to make .NET and Java systems "work and work well together".

"I want to be perfectly clear that the Microsoft commitment is there to drive interoperability and collaboration because it's good for our end users and it's good for our customers," Lewin said.

..if this was MS's intent, then why did they not do it from the start?? After all Java was around and being used when they swanned in with their 'framework'. If they'd wanted interoperability the initial design stage would've been the perfect time to do this.

Unless they want Java to do all the legwork, which is what I suspect.

It saddens me when I'm looking through job adverts for supposedly scientific computing jobs that require C# (and even more shockingly VB.NET!) experience. Unless there's something I'm not aware of and c# (and *laughs* VB) is suddenly a high-performance language. It's the 'we've got giga/teraflops to play with, so lets just waste 55% of them and it'll still seem fast' way.