3 ms·
Oh my god yes Microsoft’s naming conventions are mind boggling. .Net Standard, .Net Framework, .Net Core, and they all do slightly different things, and they s
by FridgeSeal 7y ago
Oh my god yes Microsoft’s naming conventions are mind boggling.
.Net Standard, .Net Framework, .Net Core, and they all do slightly different things, and they seemingly change with version, and now there’s .Net Framework 5, which apparently replaces/unifies some of them but it’s not super clear. Then you’ve got C# and F# and the specific language versions of those. Oh also, don’t forget the fact that there’s inexplicably like, 3 different package managers, which may or may not pull from the same place and it’s not clear what the differences are.
Coming from Python (and a little bit of Rust) I had literally no idea what was going on. I tried to learn C# twice and gave up out of sheer irritation and confusion.
- thrower123 7y agoIs there a third package manager now? There's the blessed one, NuGet, which most use, and Paket, which the cool kids and F# people use, but if there's another one out there I'm drawing a blank.
- FridgeSeal 7y agoYou can use the CLI as to do stuff. Not sure if it counts as package manager, but coming from Python, being faced with 3 different ways to install packages (I'm still not sure how environments/projects are supposed to work in .Net) certainly added to the confusion.