| C# has very minimal boilerplate for a lot of uses. I can throw together a simple CRUD UI app in WinForms in well under a day. Visual Studio handles writing all the data binding code for me, code that I'd have to write myself in any other language. Using one of the enterprise frameworks, sure, those all have boilerplate, in any language, especially the older frameworks. And for some tasks, the amount of boilerplate is tiny. I can write out a struct/class with property names matching my JSON, and watch as C# automatically data binds the JSON to a UI. The amount of boilerplate I need to do that in the browser is pretty much identical, or I can learn / figure out some fancy auto-binding toolkit that has its own boiler plate and learning curve. You can be seriously functional in C#. Passing around lambdas and using functional techniques to manipulate data has been idiomatic C# for over a decade. > I've also noticed that most C# programmers don't usually know another language Stereotyping is not good. I <3 C#, but I've written embedded C, C++, JavaScript, Typescript, and Python. If you go to most corporate dev places, you will find a significant population of single language devs. Same things happen with any popular corporate language. While I agree that learning multiple programming languages makes for better developers, blaming a language for being popular is hardly fair. Heck the number of developers who have historically only worked in C/C++ was really high for multiple decades. |