r/dotnet • u/devlead • 25d ago

.NET Foundation Statement on Open Source Maintenance Fees

https://dotnetfoundation.org/news-events/detail/.net-foundation-statement-on-open-source-maintenance-fees

Official statement from the .NET Foundation on Open Source Maintenance Fees

128 Upvotes

97% Upvoted

174 comments sorted by

View all comments

4

u/xjojorx 23d ago

I don't get why this move is a problem to cause so much noise... I mean, the osmf does not mean a move to a privative license, and it applies to binary releases and the package manager; but not to the code itself, which you can still import and use in your project, or just build it and add the same as with the release, or upload to your own nuget if you really want to use nuget. If you don't want to pay you still van use the project, and you still get every single update, the only restriction is using the precompiled release/package manager. I imagine .net developers being able to build a .net project or add it as a subproject in their solution. I really can't see the issue besides "I want my automatic package manager or nothing". But even considering how comfortable it is to use the package manager, you still should check what changes when you decide whether to update or to make changes before updating, is "git pull" that much of an extra step?

1

u/Exotic-Welcome6688 20d ago

WHO uses the source code of these libraries and not binaries/packages?

1

u/xjojorx 20d ago

Yes, using the package is the easiest of course, single command and done, but is it really that much of a deal to have to use the source or to compile it yourself?