Changes

Microsoft .Net Framework

516 bytes added, 22:01, 6 February 2014
/* Conclusion */
The following lines were added (+) and removed (-):
Microsoft applied for a multitude of extensive patents key parts of the .NET Framework.  At one time Microsoft and a competing, yet no longer industry relevant company, Novell, had an agreement to allow both use of parts of open source components of .NET, yet lock out the rest of the world programming community.  The agreement is in violation of the principles of giving equal rights to all users of a particular program.Microsoft applied for a multitude of extensive patents over key parts of the .NET Framework.  The patents were over reaching and threatened a former rival, Novell.  Microsoft and Novell formed an exclusive agreement to allow both use of parts of open source components of .NET, yet lock out the rest of the world programming community.  The agreement is in violation of the principles of giving equal rights to all users of a particular program.  Since the components in question were originally open source, the patents should never have been granted in the first place.  The practice of ripping off other people's work and stamping Microsoft on it is nothing new to the industry giant.Microsoft .NET Framework was supposed to be inherently cross platform, as promoted by Microsoft at the end of the 1990's in an effort to gain developer interest.  However, more than a decade later we see the full implementation of .NET is only supported on Microsoft Windows. Although the platform offers limited .NET subsets for other platforms, the substituted implementations of CLR, base class libraries, and compilers are all that is present.  With some degree of standardization, all implementations remain with a variety of levels of completeness when compared to the full .NET version which Microsoft provides for Windows and are too often entirely incompatible.Innovation is also limited when the user environment is limited.  Microsoft .NET Framework was supposed to be inherently cross platform, as promoted by Microsoft at the end of the 1990's in an effort to gain developer interest.  However, more than a decade later we see the full implementation of .NET is only supported on Microsoft Windows. Although Microsoft .NET offers limited .NET subsets for other platforms, the substituted implementations of CLR, base class libraries, and compilers are all that is present.  With some degree of standardization, all implementations remain with a variety of levels of completeness when compared to the full .NET version which Microsoft provides for Windows and are too often entirely incompatible. They are largely ignored by Microsoft as if only initially created to meet someone's idea of "look, we're sharing too."If you are a software developer (computer programmer) give yourself credit by investing your time into learning and developing in a better programming environment.  Microsoft .NET is for inept programmers that are incapable of learning a real programming language.  Additionally, Java developers, on average, command a much higher annual salary as compared to Microsoft .NET developers programming in VB .NET for example.  And if you are a freelance developer, do end users a favor and don't create software that requires a crappy piece of bloatware to be installed on their system just so they can use your little application.If you are a team software developer or individual computer programmer then give yourself credit by believing you are capable of learning a more powerful programming language.  Invest your time in developing in a better programming environment.  Microsoft .NET is for slackers and "quick fixers." Additionally, Java developers, on average, command a much higher annual salary as compared to Microsoft .NET developers programming in languages like VB .NET.  And if you are a freelance developer, do your end-users a favor and don't create software that requires a crappy piece of bloatware to be installed on their system just so they can use your little application.If you are an end user, try to avoid using software that requires the Microsoft .NET Framework.  Keep your computer running faster and more efficient by reducing the overhead of one or more versions of .NET on your computer.  Whatever program you wish to use that requires .NET more than likely has an alternative program made by a more talented developer that you will ultimately be more satisfied with.  And finally, if you ever are so unfortunate to purchase a piece of hardware which requires drivers and software needing the Microsoft .NET Framework, return it to the place of purchase for a full refund.  If it has anything to do with Microsoft .NET, then it is more than likely crap.If you are an end user, try to avoid using software that requires the Microsoft .NET Framework.  Keep your computer running faster and more efficient by reducing the overhead of one or more versions of .NET residing therein.  Whatever program you wish to use that requires .NET will more than likely have an alternative that is made by a more talented developer and that you will ultimately work better for you.  And finally, if you ever are so unfortunate as to purchase a piece of hardware which requires drivers or necessary software requiring Microsoft .NET Framework, return it to the place of purchase for a full refund.  If it has anything to do with Microsoft .NET, then it is more than likely crap. *** X9
Bureaucrat, administrator
16,192
edits