Feels very rare to have this kind of rug pull at the library level though, it's telling the only library in that list is a Java framework (a fellow 'enterprisey' language).
I'm not saying maintainers are obligated to work forever and never ask for money, but it's happened a lot with .NET relative to how package-light development tends to be compared to say Javascript.
Automapper and Mediatr just got announced this week.
Fluent Assertions (literally just, a fluent API for asserts) recently went commercial.
It just feels like there's a certain lethargy in the .NET ecosystem that lends itself to these switch ups. As in, .NET leans slightly towards people banging on your door because their strictly 9-5 enterprise project needs to hit some deliverable and they see their issue as your problem... while JS leans slightly towards tinkerers tinkering with stuff who are often just as needy, but are also slightly more inclined to detour to work with you, and less pressured in general.
BoorishBears|11 months ago
I'm not saying maintainers are obligated to work forever and never ask for money, but it's happened a lot with .NET relative to how package-light development tends to be compared to say Javascript.
Automapper and Mediatr just got announced this week.
Fluent Assertions (literally just, a fluent API for asserts) recently went commercial.
It just feels like there's a certain lethargy in the .NET ecosystem that lends itself to these switch ups. As in, .NET leans slightly towards people banging on your door because their strictly 9-5 enterprise project needs to hit some deliverable and they see their issue as your problem... while JS leans slightly towards tinkerers tinkering with stuff who are often just as needy, but are also slightly more inclined to detour to work with you, and less pressured in general.