I agree that Microsoft OS's have been very buggy in the past, and Windows XP carries on the tradition, but to a much lower extent. However,.NET is a totally new and different infrastructure - the server os's as well as the framework. So far in my 2 years of.NET programming experience in the corporate world, all is going good. I like Java as well, but have had bad experiences with the JVM running out of memory under Redhat and weird buggy issues with development. Either way both envoronments (.NET and J2EE) have their faults as well as their capstones. Java is portable(like you said) and.NET is flexible and fast (under windows, I have not tried mono). IMHO.
Save some time and embarassment by coding applications correctly? It is hard to put anything back together (platform and language independent) once a fatal flaw is discovered. The flaw most of the time derived from the developers...not the language. What was the internal problem anyway?
Slashdot Mirror
I agree that Microsoft OS's have been very buggy in the past, and Windows XP carries on the tradition, but to a much lower extent. However, .NET is a totally new and different infrastructure - the server os's as well as the framework. So far in my 2 years of .NET programming experience in the corporate world, all is going good. I like Java as well, but have had bad experiences with the JVM running out of memory under Redhat and weird buggy issues with development. Either way both envoronments (.NET and J2EE) have their faults as well as their capstones. Java is portable(like you said) and .NET is flexible and fast (under windows, I have not tried mono). IMHO.
Save some time and embarassment by coding applications correctly? It is hard to put anything back together (platform and language independent) once a fatal flaw is discovered. The flaw most of the time derived from the developers...not the language. What was the internal problem anyway?