To view parent comment, click here.
To read all comments associated with this story, please click here.
"I think thats a good degree of evidence, no?"
No.
.net isn't much of a competitor to Java, it's a replacement for the Windows API. Microsoft is hardly competing, they didn't implement a runtime environment for any OS besides Windows and they couldn't care less whether mono is compatible with the latest .net implementation and APIs or not.
Can you imagine the damage it would do to Microsoft if after the majority of applications for Windows have been ported to .net, someone could get a Microsoft developed, properly implemented, and up to date version of the .net rumtime environment to run those applications perfectly under Linux or OS X. Windows would loose a lot of it's major selling points if it had no exclusive software any more.
Java's selling point is portability across platforms, .net on the other hand was never implemented by Microsoft outside of Windows. If you ask me they decided .net was a good idea because it means that .net applications will run on *windows* regardless of the cpu architecture and hardware.
Microsoft is trying to replace the Windows API with .net and people know it, so of course the large share of people who were already using the Windows API will migrate to .net considering it's the future of what they're already using. If that 60% figure is accurate, all it tells me is that Microsoft is effectively replacing the older Windows API with what they envision as a way of having people compile their Windows apps only once before distributing to every hardware configuration capable of running Windows.
Calling .net a competitor to Java is true on a technical basis, but Java's target is one that .net alone isn't interested in, and that's people who want to compile a program once for it to run on several different operating systems. For all it's worth, .net is the same threat the Windows API was, except more modern and easier to use.
I agree with this, in that the fight has always been between Java and the Windows platform. Of course, Microsoft's objective is to extend the Windows platform to every computing device, from server to desktop to mobile to home theatre. Java is but a drop in the bucket compared to that.
The best move to ensure Java's survival is to focus on interoperability with the Windows platform, IMO.
Based on...? How many are running Windows that used to have a Java setup (most likely running on a non-Microsoft platform)? how many were running ASP but have moved to ASP.NET? it never actually outlines how many customers have migrated from a Java setup to a purely .NET configuration.
Like I said, is a consolidation of various technologies on the Windows platform; once complete, the .NET growth rate will go back and track against the growth rate of Windows.
You'll simply have the market split into two; Microsoft Windows and .NET and the rest; you run Windows, you'll be running .NET; and in Sun case, they don't really care about .NET because it isn't as though you can run .NET on Solaris, get support from Microsoft, and thus a real threat to Javas main benefit - multiplatform support.
That is why Java is popular at the backend; .NET is simply a replacement for an ugly way of doing things on Windows; Java on the other hand was there to solve a problem that doesn't relate to fixing an operating system problem.





Member since:
2006-07-28
"We've grown from having a quarter of the market to, now, 60 percent,"
I think thats a good degree of evidence, no?