Java takes a language-specific approach to solving problems, .NET takes a platform-specific one
Standards, and corresponding monopolies, can occur naturally
Believe it or not, there are times when I feel some empathy for Microsoft. After all, I myself was once a small-time monopolist.
Javas traditional weapon of choice
Single points of failure can be entire systems. Prevention may lie in "fencing in".
Software vendors are in a better position than enterprises to have the full-time user champions that Extreme Programming requires
Microsoft makes money from Windows desktops, not from browsers
In response to the the latest installment of my Java vs. .Net series, a number of you responded with a focus on ASP.NET. ASP.NET is Microsoft's way of delivering browser-based DHTML applications.
Two articles recently got me thinking about the fact that paradigm shifts can be born out of convenience or necessity.
What is Microsoft trying to do?
There is a natural evolution of platform technologies from document publishing to forms processing to application delivery. The Web is the leading example of this, but Adobe Acrobat PDF and Microsoft InfoPath are on their way.
Yes, you can support both