Сообщение Re[26]: почему в C# до сих пор нет наследования конструкторо от 12.12.2022 15:46
Изменено 12.12.2022 15:48 Gt_
Re[26]: почему в C# до сих пор нет наследования конструкторов?
S>Как, впрочем, и утверждения про порку.
S>Вот — про скорость: https://dusted.codes/how-fast-is-really-aspnet-core
так там как раз про отсутствие скорости у .net core и как аффторам пришлось выдавать за .net core очень специфическое приложение заточенное на этот бенчмарк, где ничего из фрейморков нет.
Not even the interface IHttpApplication comes from ASP.NET Core. This is also a custom made type which was specifically designed for the benchmark tests.
Looking further into the BenchmarkApplication.cs I was shocked by the sheer amount of finely tuned low level C# code that was tailor made for this (extremely simple) application.
Everything inside the /PlatformBenchmarks folder is custom code which you won't find anywhere in an official ASP.NET Core package.
...
ASP.NET Core has many ways of implementing routing. They have Actions and Controllers, Endpoint Routing, Minimal APIs, or if someone wanted to operate on the lowest level of ASP.NET Core (= Platform), then they could work directly with the Request and Response objects from the HttpContext.
S>Вот — про скорость: https://dusted.codes/how-fast-is-really-aspnet-core
так там как раз про отсутствие скорости у .net core и как аффторам пришлось выдавать за .net core очень специфическое приложение заточенное на этот бенчмарк, где ничего из фрейморков нет.
Not even the interface IHttpApplication comes from ASP.NET Core. This is also a custom made type which was specifically designed for the benchmark tests.
Looking further into the BenchmarkApplication.cs I was shocked by the sheer amount of finely tuned low level C# code that was tailor made for this (extremely simple) application.
Everything inside the /PlatformBenchmarks folder is custom code which you won't find anywhere in an official ASP.NET Core package.
...
ASP.NET Core has many ways of implementing routing. They have Actions and Controllers, Endpoint Routing, Minimal APIs, or if someone wanted to operate on the lowest level of ASP.NET Core (= Platform), then they could work directly with the Request and Response objects from the HttpContext.
Re[26]: почему в C# до сих пор нет наследования конструкторо
S>Как, впрочем, и утверждения про порку.
S>Вот — про скорость: https://dusted.codes/how-fast-is-really-aspnet-core
так там как раз про отсутствие скорости у .net core и как аффторам пришлось выдавать за .net core очень специфическое приложение заточенное на этот бенчмарк, где ничего из фрейморков нет.
Not even the interface IHttpApplication comes from ASP.NET Core. This is also a custom made type which was specifically designed for the benchmark tests.
Looking further into the BenchmarkApplication.cs I was shocked by the sheer amount of finely tuned low level C# code that was tailor made for this (extremely simple) application.
Everything inside the /PlatformBenchmarks folder is custom code which you won't find anywhere in an official ASP.NET Core package.
...
ASP.NET Core has many ways of implementing routing. They have Actions and Controllers, Endpoint Routing, Minimal APIs, or if someone wanted to operate on the lowest level of ASP.NET Core (= Platform), then they could work directly with the Request and Response objects from the HttpContext.
In fact, you won't find a HttpContext anywhere at all. It's almost like the .NET Team tried to avoid using ASP.NET Core at all cost, which is strange to say the least.
S>Вот — про скорость: https://dusted.codes/how-fast-is-really-aspnet-core
так там как раз про отсутствие скорости у .net core и как аффторам пришлось выдавать за .net core очень специфическое приложение заточенное на этот бенчмарк, где ничего из фрейморков нет.
Not even the interface IHttpApplication comes from ASP.NET Core. This is also a custom made type which was specifically designed for the benchmark tests.
Looking further into the BenchmarkApplication.cs I was shocked by the sheer amount of finely tuned low level C# code that was tailor made for this (extremely simple) application.
Everything inside the /PlatformBenchmarks folder is custom code which you won't find anywhere in an official ASP.NET Core package.
...
ASP.NET Core has many ways of implementing routing. They have Actions and Controllers, Endpoint Routing, Minimal APIs, or if someone wanted to operate on the lowest level of ASP.NET Core (= Platform), then they could work directly with the Request and Response objects from the HttpContext.
In fact, you won't find a HttpContext anywhere at all. It's almost like the .NET Team tried to avoid using ASP.NET Core at all cost, which is strange to say the least.