7 ms·
A lot of people in the C# community actually use Paket (F#'s package manager) because NuGet is a complete shit-show. I'm about to do that change myself, because
by moogly 8y ago
A lot of people in the C# community actually use Paket (F#'s package manager) because NuGet is a complete shit-show. I'm about to do that change myself, because NuGet is truly one of the worst package managers I've ever used (and that is saying something).
- brianberns 8y agoI’m an F# developer in a C# shop, so I’ve only used NuGet. Can you enumerate some of the advantages of Paket?
- chusk3 8y agoparaphrasing from the main site(https://fsprojects.github.io/Paket/ https://fsprojects.github.io/Paket/): > Paket is a dependency manager for .NET and mono projects, which is designed to work well with NuGet packages and also enables referencing files directly from Git repositories or any HTTP resource. It enables precise and predictable control over what packages the projects within your application reference. The big change is solution-level dependency management instead of the nuget-default project-level management, so you always have the same versions of dependencies across all projects in a solution. It also uses a lockfile for these versions so that restores are idempotent. It also allows for fetching independent files from HTTP-accessible locations or git repos, which is nice in F# because the language is succinct and enables you to reuse modules without going through the rigamarole of making and publishing nuget packages.
- pjmlp 8y agoI use .NET on and off since the pre-beta days (priviledges of working at an MSFT partner) and never seen anyone use Paket, other than on F# tweets.
- JamesBarney 8y agoThis is different from my experience. I've find that I run into 10 npm issues for every nuget issue.