3 ms·

I'm glad you had the balls to come out and say this here..on HN. I'm a .NET/C# dev as well (as labelled by recruiters and companies hiring me). There's a time

I'm glad you had the balls to come out and say this here..on HN. I'm a .NET/C# dev as well (as labelled by recruiters and companies hiring me). There's a time to play with new shiny objects, and there's a time when you have to get real work done. If anyone here hates on you because you can get shit done with your preferred language...they're just jealous of your productivity.

dimgl 11y ago
It doesn't take "balls" to say anything anonymously on an online forum. Nobody's angry he likes C#; there simply is no reason for this comment to exist on a thread about Go. I've done C# development for many years. C#, while elegant, is far from being a productive language, mostly because of its ecosystem and community. Making a simple API web server using proprietary Microsoft libraries is way harder than it needs to be. Documentation is also piss-poor on most of these tools, and many developers just resort to reading opinionated online web blogs which give all kinds of terrible advice. You can use open-source libraries like Nancy instead, but they're usually error-prone and updates have been known to break production deployments. Visual Studio still crashes all the time and compilation on bigger projects is usually slow and painful. I've had to work on full fledged projects with infamous Entity Framework data-access layers and these things are a nightmare to work with. I've seen entire projects generated using T4 text templates... As feature-rich as the language may be, the way developers use it lead to huge problems. Now that Microsoft is introducing ASP.NET Core the fragmentation in the community is only getting worse. Couple this with the fact that .NET is used in all sorts of dysfunctional development teams, and you've got a recipe for disaster every time. C# is not a productive language.

dimgl 11y ago

It doesn't take "balls" to say anything anonymously on an online forum. Nobody's angry he likes C#; there simply is no reason for this comment to exist on a thread about Go. I've done C# development for many years. C#, while elegant, is far from being a productive language, mostly because of its ecosystem and community. Making a simple API web server using proprietary Microsoft libraries is way harder than it needs to be. Documentation is also piss-poor on most of these tools, and many developers just resort to reading opinionated online web blogs which give all kinds of terrible advice. You can use open-source libraries like Nancy instead, but they're usually error-prone and updates have been known to break production deployments. Visual Studio still crashes all the time and compilation on bigger projects is usually slow and painful. I've had to work on full fledged projects with infamous Entity Framework data-access layers and these things are a nightmare to work with. I've seen entire projects generated using T4 text templates... As feature-rich as the language may be, the way developers use it lead to huge problems. Now that Microsoft is introducing ASP.NET Core the fragmentation in the community is only getting worse. Couple this with the fact that .NET is used in all sorts of dysfunctional development teams, and you've got a recipe for disaster every time. C# is not a productive language.