News for hackers. Stuff that matters.
Re:Why I'm no longer giving up on C# by skrebbel on Monday July 22, 2013 @04:14PM (#6086186)
This. A thousand times this.

I love C#, I'm quite fond of Visual Studio and Xamarin Studio, but I dread nearly all the auxiliary MS libraries, like WCF, ASP.NET MVC, MSMQ, WCF Data Services, MSTest, and so on. WPF (MS's most recent UI framework) is an odd one out though, cause it kicks butt. Must've been a different team. But yeah, it's terribly platform-specific so not very useful in web tech.

I never understood why so many C# programmers automatically default to these MS technologies without even looking around. This bugs the crap out of me, because the attitude gives C# (and other .NET languages) a bad name undeservedly, and it really limits further development of the ecosystem. Which is a shame, because as this blog post points out, there's a good bunch of really good .NET open source out there.

I very much miss ServiceStack in the list, though. ServiceStack must be the best designed API/backend framework that I've ever used, in any language. The moment you want to handle more than a few URL requests, it beats Nancy hands down. Stuff gets clearer, there's less magic, and somehow you also end up with less code.

Re:Why I'm no longer giving up on C# by dragonwriter on Monday July 22, 2013 @04:25PM (#6086237)
> I never understood why so many C# programmers automatically default to these MS technologies without even looking around.

Many C# programmers are C# programmers because they (or, in many cases, their employers) default to MS technologies without even looking around.

Re:Why I'm no longer giving up on C# by adamconroy on Monday July 22, 2013 @08:02PM (#6087327)
Alternatively, many c# programmers use the default stack because they don't treat their client/employer as their personal playing field to try out the latest buzz.
Re:Why I'm no longer giving up on C# by PommeDeTerre on Monday July 22, 2013 @09:14PM (#6087583)
It wasn't that long ago that ASP.NET MVC, EF, and WCF, for example, were new technologies.

How were the early adopters of those unproven technologies not "treating their client/employer as their personal playing field to try out the latest buzz"?

Re:Why I'm no longer giving up on C# by adamconroy on Tuesday July 23, 2013 @01:49AM (#6088438)
The point is that as an architect you can be very confident that those frameworks will be solid, well maintained and documented and quite importantly well integrated with everything else in the default stack now and in the future. You can also be confident that in the future you will be able to find developers with experience using the default stack. I could bore you with quite a few personal anecdotes that back up my opinions.

Of course there are going to be exceptions to this but as a general rule, taking into account all dimensions of the decision, the default stack is the rational choice.

Re:Why I'm no longer giving up on C# by spamizbad on Monday July 22, 2013 @10:07PM (#6087756)
There are actually many Microsoft shops that still consider the stuff you listed as too new/unproven.

In general, .NET shops are more risk adverse than "open source" shops. Some reasons are cultural, some are business. I think Microsoft is trying to change this as they're clearly growing tired of their own developer base being reluctant to adopt their own technologies.

Re:Why I'm no longer giving up on C# by adamconroy on Wednesday July 24, 2013 @01:13AM (#6094623)
Re:Why I'm no longer giving up on C# by Maarten88 on Monday July 22, 2013 @04:58PM (#6086421)
A project I worked on at a large corporate client got into serious problems after it got audited, and they found we were using several non-Microsoft libraries. They wanted us to remove those and use "supported" libraries such as Unity and EntLib.