Why .net is slow

irender

Member
Joined
month_3_short 18, 2015
Messages
8
Reaction score
0
Because .net has a lot of dependencies. It cannot run by itself. It needs the .net framework before you can run it.
 

Git

Member
Joined
month_2_short 9, 2010
Messages
55
Reaction score
41
Age
36
Because almost every command makes calls to the framework, and is range checked, memory securely allocated, checked when free, etc. Compared to direct compiled C it becomes very slow. But, you must also weigh against that how much work is being done by each line of code, and how long it would take to write the same functionality in a simple language. There are always pros and cons, nothing for free.

Git
 

Sarracino

Member
Joined
month_9_short 30, 2009
Messages
5
Reaction score
0
Age
46
Because almost every command makes calls to the framework, and is range checked, memory securely allocated, checked when free, etc. Compared to direct compiled C it becomes very slow. But, you must also weigh against that how much work is being done by each line of code, and how long it would take to write the same functionality in a simple language. There are always pros and cons, nothing for free.

Git
and the libraries are all dynamics and very small... you can try to exclude in your av program the .net fw dir
 

AbdulAbdalla

Member
Joined
month_9_short 3, 2009
Messages
18
Reaction score
3
Age
39
.NET is not native code. It gets compiled to an intermediate language which is then JIT compiled during execution. That of course takes more time than executing native code in the first place.
 
Top