Linked by Thom Holwerda on Tue 26th Jul 2005 20:48 UTC
Thread beginning with comment 9427
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links




Member since:
2005-06-29
When you put together the words "totally indifferent" with "it’s great what they’re doing", you can see what I mean by Microsoft being in two minds about Mono.
This guy has a hard time playing jr. shrink. Many people at Microsoft (at least engineer types) like that others are implementing the platform, but it doesn't mean that they're going to help them out with the project (that's the indifferent).
The Grasshopper compiler converts your compiled ASP.NET project into Java byte code, for deployment on a J2EE application server;
I don't know much about ASP.NET, but I would presume this grasshopper tool would have a hard time converting all C# code (pointers for one thing), rather than IKVM which can easily handle Java bytecode
Interesting take on J2EE being a pain to develop with. Seems to be a big demand for J2EE developers. Maybe developers are getting sick of working with it.