Re: Re: Re: Missing the point
When I say 40-50% of apps, am referring to desktop apps written for Windows. You have to realize, that it is extreamly hard to do anything in the two latest visual studio incarnations without wanting a feature from .NET. You can program .NET in C++, C#, J++, VB....plus other 3rd party languages. You also have to realize that .NET is a replacement of the Windows API, not a follow on like MFC. The .NET APIs are designed to fully replace, and in many cases have more capabilities than the Windows APIs. Infact, other than syntax, System.Windows.Forms is very much like Cocoa's window manager in the way everything interacts with the users code....of course, no NIBS. But very much the same structure to the classes.
There are some things you still can't do in .NET....which is why you can involke non .NET code libraries. But most of it is there, infact DirectX 9 interfaces with .NET. Now you can program games in .NET, and with code caching, .NET saves the compiled code after it is ran the first time, to speed applications up. Much better than Java recompiling everytime you run an app.
BTW, when I say 40-50% what does it include?
Windows Explorer in Windows Longhorn
Upcoming Microsoft Office release
Visual Studio is entirely written in .NET
Why are application developers switching?
Simple, integrated XML data archiving from all objects, very well tuned data table/row interface called ADO.NET, which interfaces with MS SQL, ODBC, Oracle, and MySQL (with 3rd party MySQL adapter). Infact, you can take data from the database, give it a schema, and spit it out as XML, or bind it to controls, and your application can automatically navigate through data. Very nice, very code efficient.
So when I say 40%-50%, I can guarentee that for Windows applications the movement is there. In addition, checkout your local bookstore. Barns & Noble has 10x the .NET books than it does Java or C / legacy VB. Developers who work with it love it, preach it, and know it makes their lives easier.
I must add however, MS will not make cross platform their goal. While it is like Java in that its able to go cross platform, its been left to the open source community to make it work on other platforms. So again, anyone with PPC assembly experience is urged to look at Mono. That project is in need of a PPC compiler, as it only works under an interpreter for PPC at this time.
Originally posted by eric_n_dfw
I agreed with everything else you said, but this part made me raise an eyebrow. Now, I'm a server side developer who's been working on J2EE and Unix C/C++ for several years, so maybe I'm out of touch with desktop software, but are you sure about that number?
When you say .NET (of which I'll admit, I have 0 experience with) do you mean Windows app's written using .NET studio? In which case I'd say that .NET is just the next gen of Microsoft's Windows API's like when they migrated to MFC back in the 90's.
I'd be interested in reading any supporting data you have on this 40-50% claim.
When I say 40-50% of apps, am referring to desktop apps written for Windows. You have to realize, that it is extreamly hard to do anything in the two latest visual studio incarnations without wanting a feature from .NET. You can program .NET in C++, C#, J++, VB....plus other 3rd party languages. You also have to realize that .NET is a replacement of the Windows API, not a follow on like MFC. The .NET APIs are designed to fully replace, and in many cases have more capabilities than the Windows APIs. Infact, other than syntax, System.Windows.Forms is very much like Cocoa's window manager in the way everything interacts with the users code....of course, no NIBS. But very much the same structure to the classes.
There are some things you still can't do in .NET....which is why you can involke non .NET code libraries. But most of it is there, infact DirectX 9 interfaces with .NET. Now you can program games in .NET, and with code caching, .NET saves the compiled code after it is ran the first time, to speed applications up. Much better than Java recompiling everytime you run an app.
BTW, when I say 40-50% what does it include?
Windows Explorer in Windows Longhorn
Upcoming Microsoft Office release
Visual Studio is entirely written in .NET
Why are application developers switching?
Simple, integrated XML data archiving from all objects, very well tuned data table/row interface called ADO.NET, which interfaces with MS SQL, ODBC, Oracle, and MySQL (with 3rd party MySQL adapter). Infact, you can take data from the database, give it a schema, and spit it out as XML, or bind it to controls, and your application can automatically navigate through data. Very nice, very code efficient.
So when I say 40%-50%, I can guarentee that for Windows applications the movement is there. In addition, checkout your local bookstore. Barns & Noble has 10x the .NET books than it does Java or C / legacy VB. Developers who work with it love it, preach it, and know it makes their lives easier.
I must add however, MS will not make cross platform their goal. While it is like Java in that its able to go cross platform, its been left to the open source community to make it work on other platforms. So again, anyone with PPC assembly experience is urged to look at Mono. That project is in need of a PPC compiler, as it only works under an interpreter for PPC at this time.