3 ms·
To be fair: .NET (Framework) was not fast in the past. It was not. It was really slow. It was exclusively on Windows, IIS, some worker module, piped through a W
by oaiey 6y ago
To be fair: .NET (Framework) was not fast in the past. It was not. It was really slow. It was exclusively on Windows, IIS, some worker module, piped through a Webforms optimized System.Web dll and most of that code not optimized for memory usage etc.
But that is over with modern .NET Core. Nothing of above is valid anymore and the result is wicked fast as your link shows as evidence.
- aliswe 6y agoOaiey, .NET is not synonymous with WebForms.
- oaiey 6y agoI know. But System.Web has much technical debt it cannot give up because WebForms is still around in the .NET Framework. I would recommend some early talks from Damian Edwards or David Fowler about ASP.NET Core. They are very explicit about that (in the end they build Katana replacing System.Web on .NET Framework to allow a better ASP.NET MVC performance, which lead to Project "K", which lead to (ASP).NET Core). Speaking as one fanboy to another ;)
- manigandham 6y agoThe webforms stuff was slow, but MVC was quicker and has been around for a long time, along with basic HTTP handlers. If you stepped down a 1-2 levels of abstraction, you could get very good performance. But yes, those tricks are now obsolete and the platform is incredibly fast.