Changes

Microsoft .Net Framework

35 bytes removed, 21:47, 6 February 2014
/* Limited Options for Developers */
The following lines were added (+) and removed (-):
Using Microsoft Visual Studio 6.0 a software developer (computer programmer) could create a stand alone executable that could be distributed to end users without the end users needing to deal with installing a "framework" to run and use the software.  Sure, there was libraries and components that sometimes needed to be installed along with the executable, however, this could be accomplished transparently though an installer, and is not out of the ordinary for software developed in any platform.   Using Microsoft Visual Studio 6.0 a software developer (computer programmer) could create a stand alone executable that could be distributed to end users without the end users needing to deal with installing a prerequisite "framework." Sure, there are certain components that sometimes needed to be installed along with the executable, however, this could be accomplished transparently though an installer, and is not out of the ordinary for software developed in any platform.   Java programs created for distribution require Java Virtual Machine, a special framework, in order to run on the end user computer.  This can be a burden just like end users having to deal with Microsoft .NET Framework.  However, there is a huge advantage that Java developers have over Microsoft .NET developers, JAVA can run on many platforms (Mac, PC, *NIX).  This benefit provides an over-weighing factor tipping the scale in favor of Sun's JAVA - in other words, making it worth while to develop software in JAVA.  Microsoft .NET developers are stuck with the whole framework crap and are still limited to Microsoft Windows end users only.  What's the point of the .NET Platform besides a few shared libraries and the limited language interoperability it offers?  Certainly not enough to tip the scale in favor of developing in the .NET Platform.Java programs created for distribution require Java Virtual Machine, a special framework, in order to run on the end user computer.  This can be a burden much the same as Microsoft .NET Framework.  However, there is a huge advantage that Java developers have over Microsoft .NET developers, JAVA can run on many platforms (Mac, PC, *NIX).  This benefit provides an over-weighing factor tipping the scale in favor of Sun's JAVA - in other words, making it worth while to develop software in JAVA.  Microsoft .NET developers are stuck with the whole framework crap and are still limited to Microsoft Windows.  What's the point of the .NET Platform besides a few shared libraries and the limited language interoperability it offers?  Certainly not enough to tip the scale in favor of developing in the .NET Platform.Furthermore, there is ZERO backwards compatibility.  Microsoft loves to pull the rug out from under developers and end users alike.  With the introduction of the .NET framework, the Visual Basic language was replaced by the Visual Basic .NET language.  The replacement was not backwards compatible and forced programmers to relearn something.  Not only did it force programmers to update their knowledge on use of the syntax, but their entire concept of programming had to be changed radically.  Microsoft forced their aborted version of the Object Oriented programming model on developers. Furthermore, there is ZERO backwards compatibility.  Microsoft loves to pull the rug out from under developers and end users alike.  With the introduction of the .NET framework, the Visual Basic language was replaced by the Visual Basic .NET language.  The replacement was not backwards compatible and forced programmers to relearn all but B.A.S.I.C. itself.  Not only did it force programmers to update their knowledge on use of the syntax structure, but their entire concept of programming had to be changed radically.  Microsoft forced their aborted version of the Object Oriented programming model on developers.
Bureaucrat, administrator
16,192
edits