This is a great example of what is wrong with with dotnet. Someone who has been doing their best to improve the situation and finally giving up, after years of effort is dismissed by some random .net programmer as, "...pointing his finger in the wrong direction" or "using the wrong tools to solve the problems he works on".
C# is an incredible language and VS w/ R# is a pleasure to work with. I have been working in this stack for over 6 years, so it is fair to say I have enough experience to know what I am talking about with regards to being a .NET developer.
That said, .NET, as a development platform, is a couple of diamonds covered by tons of shit and surrounded by people trying to convince everyone else their shovel has all the goodies. Microsoft's shovel comes up empty more often than not and each year sees fewer people sifting through it all to help guide those without the time or taste for it. The biggest killer of .NET is that the majority of the community seems content to keep taking spoonfuls from the MS shovel lying to themselves about it's content.
> Someone who has been doing their best to improve the situation and finally giving up,
What I see is a random blogger makes generalized statements based on lack of experience.
> so it is fair to say I have enough experience to know what I am talking about with regards to being a .NET developer.
Your experience counts, just not mine! And you also know what you're talking about!
> That said, .NET, as a development platform, is a couple of diamonds covered by tons of shit and surrounded by people trying to convince everyone else their shovel has all the goodies.
You seem to have a lot of anger.
Thanks for trying .NET.
Have a nice day.
P.S., more than likely the blog author used VS.NET in a "visual" capacity (drag-and-drop component building).
Is it more likely than say a polyglot, unix loving, vim user who automates even .NET tasks with rake scripts and enjoys long walks on the beach also being sexually attracted to destroying every software project by dragging and dropping in a completely broken visual design paradigm?
I was trying to shape why this is an issue to the community that you and I are a part of. I don't know the author personally, but had heard of him before this blog post. The departure of individuals and those like him is a serious problem and will, in my opinion, ultimately kill the platform. Dismissing this problem will not solve it.
C# is an incredible language and VS w/ R# is a pleasure to work with. I have been working in this stack for over 6 years, so it is fair to say I have enough experience to know what I am talking about with regards to being a .NET developer.
That said, .NET, as a development platform, is a couple of diamonds covered by tons of shit and surrounded by people trying to convince everyone else their shovel has all the goodies. Microsoft's shovel comes up empty more often than not and each year sees fewer people sifting through it all to help guide those without the time or taste for it. The biggest killer of .NET is that the majority of the community seems content to keep taking spoonfuls from the MS shovel lying to themselves about it's content.