4 ms·
The problem, and I say this being 22 years deep in it, is that .NET was never cool. That seems unimportant, but being objectively the best thing going doesn’t
by highwaylights 3y ago
The problem, and I say this being 22 years deep in it, is that .NET was never cool.
That seems unimportant, but being objectively the best thing going doesn’t build a community or any word-of-mouth around your product.
I’d love to think we’d see a thriving Nuget scene on the order of npm or gem, but if it was going to happen it would’ve happened by now.
- theshrike79 3y agoYeah, it took a LONG time for .NET and C# to get out of the "Micro$oft Bad" -reputation. But having done a good 15 years of Enterprise Java professionally and having moved to C# for the last half decade, there isn't enough money in my country's IT salaries for me to go back to Java. It's not just the language, it's the whole ecosystem that's icky compared to C#/.NET.
- cxr 3y agoSolution: cajole people from the community into effectively rebranding themselves into something sexier through a somewhat hostile fork run by competent people who "get it" and are not (currently) affiliated with MS. People love throwing support behind the rebels. Make sure to rebrand the whole thing, though. References to "C#" and ".NET" shouldn't appear anywhere except on the project's /about/history page.