The following lines were added (+) and removed (-):
Criticism of Microsoft .NET Framework from the developer's perspective differs form that of the end user. To the end user, it is an annoying thing that the end user ends up discovering he or she needs to have installed in order to get some program just downloaded to work. Then, the next time some software is installed requiring Microsoft .NET Framework, it needs yet a different version and that has to be installed. Eventually the end user has a sluggish running computer loaded up with multiple versions of .NET Framework in Windows, because each new release is NOT backwards compatible, and there are often internal conflicts caused by the existence of multiple versions of .NET Framework on the same machine. Criticism of Microsoft .NET Framework from the developer's perspective differs form that of the end user. To the end user, .NET Framework is an annoying thing suddenly needed by some software he or she is trying to install. Then, the next time some other software is installed requiring Microsoft .NET Framework, it needs yet a different version and that has to be installed. Eventually the end user has a sluggish running computer loaded up with multiple versions of .NET Framework, because each new release is NOT backwards compatible, and there are often internal conflicts caused by the existence of multiple versions of .NET Framework on the same machine. ''Another annoyance the end user often discovers is that the software he or she is attempting to install doesn't even mention the .NET Framework requirement until well into the installation process. The user might see a message like, "Attempting to connect to xxx.micorosft.com to install the Microsoft .NET Framework." "Conenction Time Out, aborting installation!" It would be nice to know that a massive external software environment is required before trying to install some new program just downloaded off the net!''