From: Pete Dashwood on 20 Apr 2010 18:57 People who read this forum regularly will know that I am a great fan of Microsoft's .NET platform. For me, the main attraction is that it is an environment which supports Objects and Layers without requiring any particular language (components can run in it easily, without even requiring to be written in a .NET language; the interface between managed (.NET) and unmanaged (non-.NET) components is completely seamless), and it includes around 100,000 pre-written, pre-debugged Classes which allow not only a rich source for application development, but also better and easier control of the Windows environment than has previously been available. Previously, it was necessary to make Win API calls to do stuff, now all of this is available seamlessly through standard classes and objects. The Language Integrated Query (LINQ) implementation makes SQL look kludgy, (although LINQ necessarily generates SQL at the moment, because that is what the current RDBMS platforms recognise. For future technology and particularly parallel processing on multiple cores, LINQ is a quantum leap ahead.) So, as you may have gathered, I really like this platform and have never regretted moving to it. But is it perfect? Some people don't think so, although nobody I know who has worked with it, would give it up. Here is a very well balanced article with opinions expressed by competitors of Microsoft and defended by MS.Some very valid points are raised, but there is nothing here that would persuade me to move away from .NET. Rather, this article gives some insight into the kind of problems faced by any vendor when trying to be all things to all people... http://www.sdtimes.com/link/34183 Pete. -- "I used to write COBOL...now I can do anything."
From: Kulin Remailer on 21 Apr 2010 08:03 Maybe IBM should buy Microsoft, kill Windows, and replace it with OS/2? :-) Dare to dream!
|
Pages: 1 Prev: rtsora32 error codes Next: Microfocus Express.net Compilier |