Criticism Of Microsoft .NET Framework 



There are some concerns related to .NET and also criticism of Microsoft .NET Framework. We are going to take a look at the points of concerns regarding Microsoft .NET Framework in the below review.


  • One of the main points of criticism of Microsoft .NET Framework is that many applications running in a managed environment tend to utilize greater number of resources of the system as compared to the other application of same type which access machine resources more directly.


  • Among other concerns regarding Microsoft .NET Framework is that Unobfuscated managed CIL bytecode can easily be reverse-engineered as compared to its native code. There is an issue with the over possible loss of trade secrets and the bypassing of license control mechanisms.


  • The newer versions of the Microsoft .NET framework such as 3.5 and later versions are also responsible for the criticism of Microsoft .NET Framework. Because these versions are not pre-installed in versions of Windows below Windows 7. This is the reason because of which these applications must lead users without the framework through a procedure to install it. There are many experts who have raised concerns regarding Microsoft .NET Framework’s large size runtime installers for end-users. 


  • One of the other reasons behind Microsoft .NET Framework criticism is that at present it does not offer ant sort of support for calling Streaming SIMD Extensions (SSE) via managed code. But Mono has offered support for SIMD Extensions as of version 2.2 within the Mono.Simd namespace.


  • Criticism of Microsoft .NET Framework is also done because of the fact that the standards on which Microsoft .NET has been built up are inherently cross platform. Thus, Microsoft's full implementation of .NET is only supported on Windows. However, it offers limited .NET subsets for other platforms. The substituted implementations of the CLR, base class libraries, and compilers are also there. Despite the fact that all similar standards have been used to develop these implementations, still they are different implementations with varying levels of completeness when compared to the full .NET version which Microsoft provides for Windows and are on occasion incompatible.