3 ms·
> Professionally I've only ever worked in c# code bases. Pretty much answered their own question in sentence one. In my opinion OP is delusional. I worked in
by asp_hornet 3y ago
> Professionally I've only ever worked in c# code bases.
Pretty much answered their own question in sentence one.
In my opinion OP is delusional. I worked in .net for 13 years and was stoked to leave. The layers of indirection, obtuse abstraction and over application of design patterns in “idiomatic c#” is preposterous.
- danielovichdk 3y agoHaving worked professionally with .net for +20 years I have to admit that you have a good point. There are a lot of dogmatism tied to the platform, it's community ecosystem sucks and there is no real lust to go further than what Microsoft offers. On the other hand, you can easily have a programming career in .net alone. Its not going away the next 30 years.
- asp_hornet 3y agoWell said. Its nothing to do with the language or tooling, just this weird ingrained dogma. > On the other hand, you can easily have a programming career in .net alone. Its not going away the next 30 years. Not to mention if a service offers an official client or SDK, C# is almost always on that list. That is awesome.
- andyjohnson0 3y ago> The layers of indirection, obtuse abstraction and over application of design patterns in “idiomatic c#” is preposterous. I don't think this is a problem that is specific to .net. These issues will be found in many large codebases built on platforms that are popular for enterprise development, such as Java.