4 ms·
I have worked pretty much my whole career in .NET, and I think it's pretty good in terms of actual coding and development. It has gotten better by leaps and bou
by funkah 15y ago
I have worked pretty much my whole career in .NET, and I think it's pretty good in terms of actual coding and development. It has gotten better by leaps and bounds in recent years. .NET and C# aren't the problem, the insanity of the Windows stack is the problem. So many stupid little things unrelated to your code can go wrong, the toolchain is paltry, and deployment is still a mess.
If you're actually using drag-and-drop you probably already lost.
- InclinedPlane 15y agoC# is an awesome systems language, hampered primarily by official support being limited to windows systems. But a lot of other technologies swirling around the .net stack are horrific. EF, workflow/xaml, wpf, and even the build infrastructure such as team foundation and msbuild are not a pleasure to work with and in many cases generally inferior to free open source alternatives. Worse yet, sometimes you get the feeling that building expertise in all these tools is limiting because it has little commonality outside the windows bubble. Working on improving IIS performance won't help you much in a wider world were apache and nginx expertise is more useful, for example.
- deleted 15y ago[deleted]