3 ms·
> I know it's not a 100% fair comparison, since I am biased. It might also have something to do with you apparently unironically comparing a framework to a pro
by filleduchaos 7y ago
> I know it's not a 100% fair comparison, since I am biased.
It might also have something to do with you apparently unironically comparing a framework to a programming language.
- mschuster91 7y ago.net is both framework and language, for the framework comes with the language.
- efdee 7y ago.NET is not a language at all. C# is, VB.NET is, F# is. .NET, not as much.
- xeonoex 7y agoI'm not sure that you understand what .NET is. .NET is a platform/ecosystem. I was talking about packages. Packages are managed by nuget, which works across all .NET languages, which is why I didn't specify a language.
- filleduchaos 7y agoFramework, platform, ecosystem, SDK, etc: you're rather neatly sidestepping the point that you're comparing not a programming language to programming languages. A fair comparison would be C# to Java, or Javascript. What Microsoft chooses to call the .NET Standard Libraries is not at all the same thing as a language's standard library.
- xeonoex 7y agoHow is that relevant at all? We're talking about package management. .NET uses nuget. Let's look at the nuget site: https://www.nuget.org/ https://www.nuget.org/ > NuGet is the package manager for .NET. So my point is invalid because I wrote .NET instead of C#/VB/F#? You might want to contact nuget to tell them their site is wrong too then. My point is that finding quality packages is easier with nuget than the JS or Java package managers. And using them is usually easier too. It's a fair comparison.