To view parent comment, click here.
To read all comments associated with this story, please click here.
But M$ in a very good position. Easier to port the existing Visual Basic, C++, Delphi code to .NET to Java. The .NET environment give a language-independent class library and give a common CLR to every language. There are COBOL, RPG, Python, Object Pascal, etc. implementation for .NET.
Try vb 6 to .net sometime, and tell me how easy it is ;-) but in general, your right. this is one of the coolest things about .net.
It is true, but the major reason: the java is NOT changed to API. No databindnigs, no client-side database cache, etc. Yes, there are some independent development, but there is not any only one widely accepted. With ADO.NET any company can develop data-bounded web controls, windows.forms controls or any external components.
Im not sure what you mean there. API stands for application programmers interface, and java has a better API then .net (or anything else ive ever used, its a cross platform os encapsulation). Data bindings and client side caching are very specific to the visual studio way of doing things, you are talking about VS code generation. And if you are going to tell me ASP offers more power to the developer then JSP, ill have to call bullshit. And say what you will about swing, its crime is over engineering, not under engineering. its power is staggering, unfortunately, so is the amount of code required to do anything (properly).
Data bindings and client side caching are very specific to the visual studio way of doing things, you are talking about VS code generation.
It is not only a visual studio way, all modern RAD-oriented systems use it (Delphi, Visual Studio, etc). And the most of professional java environments (JBuilder, Oracle JDeveloper, etc) also support it, but this tools are uses their own cached dataset versions. It can be very important if you creata applications with many forms and data elements.




Member since:
This is the race and Microsoft does everything wrong it can: win32-winforms-avalon - 3 API changes in only several years. That's why .NET hasn't been adopted until now [except by ATI and HP]. The one who manages to move the majority of the code base from unmanaged to managed will rule upcoming 20 years of IT.
But M$ in a very good position. Easier to port the existing Visual Basic, C++, Delphi code to .NET to Java. The .NET environment give a language-independent class library and give a common CLR to every language. There are COBOL, RPG, Python, Object Pascal, etc. implementation for .NET.
And yes, while Java is a very consistent development environment, it is not usable for such a task.
It is true, but the major reason: the java is NOT changed to API. No databindnigs, no client-side database cache, etc. Yes, there are some independent development, but there is not any only one widely accepted. With ADO.NET any company can develop data-bounded web controls, windows.forms controls or any external components.