5 ms·
At least .NET is very capable of allowing you to support third party libraries. Heck, even ASP .NET Core isn't built-in anymore, you get it through NuGet. So yo
by giancarlostoro 3y ago
At least .NET is very capable of allowing you to support third party libraries. Heck, even ASP .NET Core isn't built-in anymore, you get it through NuGet. So you're not stuck with the standard libraries.
- wiseowise 3y ago“Don’t you guys have internet?” What happened to batteries-included support?
- giancarlostoro 3y agoASP isnt included OOTB anymore, so if you want to do web dev in .NET you have to install it, they decoupled a ton of things from the core of the language.
- neonsunset 3y agoYou don’t get it through NuGet. You get it by specifying the sdk type in the project. https://learn.microsoft.com/en-us/dotnet/core/project-sdk/overview https://learn.microsoft.com/en-us/dotnet/core/project-sdk/ov...
- giancarlostoro 3y agoUsed to be this way for .NET Core, I guess with modern .NET they changed it? https://www.nuget.org/profiles/aspnet https://www.nuget.org/profiles/aspnet Some projects listed were last updated in 2022.
- metaltyphoon 3y agoASP comes included in SDK. All you need is to specify in the csproj that you want a Web project
- Smaug123 3y agoBut when you're replacing, like, much of the standard library, you have to be a bit sad about all the interop work that falls on the user. It should instead fall on the makers of the bad standard library.
- giancarlostoro 3y agoMicrosoft is more likely to just create new alternative libraries / classes to the standard library. They drop new things all the time that improve on old approaches. Look at every way you can make a GUI in .NET from Microsoft as an example of this. People have no issue using third party libraries in other languages to get more done than the OOTB libraries.