Not to say .NET can't still be the right choice. Just that there are other points to consider other than strictly personal preference. You could argue for an MVP this isn't the case but honestly I think being in a position where you have to do a full rewrite a year later is in some ways worse than facing a (hopefully slight) learning curve when starting out.
Any link? That seems to be pretty much wrong.
If you don't like those, pango2 aims to provide django-esque templates for go; things like martini, gin-gonic, and negroki provide nicer routers; and Gorilla aims to provide a good deal of web-server-y things.
Long time developer here, came from vs to eclipse and later Netbeans and Idea:
Tell me: don't you still have to buy resharper to get the same refactoring tools that I get for free in eclipse?
Until recently the meme among tje fanboys seemed to be "VS is the best ide" (i.e.: after you have installed resharper).
Are all modern refactoring tools installed ootb with vs 2013 or 2014?
with the advent of roslyn and the compiler api i would be you'll be seeing more and more built into visual studio, or at the very least broken off into free community extensions as the 'guts' of writing these kinds of plugins will get much easier.
i still vastly prefer vs to eclipse just because of responsiveness alone; the core features are great, and i pay for resharper too because it's a great tool worth the money.
C#'s one of the best languages in town and the IDE's the unchallenged best in town by a long way. And the SQL product is amazing, much better than MySlowQL.
So what bit is better? Deployment? Hosting? I'm genuinely asking here, you're just waving hands.
I've used both, the thing that puts me off .Net is the lack of choice when new stuff comes out (like elasticsearch, or a new language, or something like Docker) as it usually takes a year or so before it's easy to use on Windows, but that's about it.
The debugging experience is the key. The best thing a VS user can do to boost productivity substantially is learn how to use the debugging tools (navigating the stack, using Debug output messages, conditional breakpoints, the immediate window, autos and locals, etc.)
The plugin and extension community is awesome. There are two extensions every (web) developer needs - Web Essentials and Productivity Power Pack. These two are produced unofficially by MS teams as a platform for experimental features that may or may not make it into future VS versions.
Refactoring and code correctness is so much better in VS. Code Analysis, StyleCop, and third-party tools like Resharper make it a snap to analyze and correct code that may cause issues in the future.
This, and the planning tools that TFS gives us out of the box (whether you use git or the tfs vcs) is a boon to developer productivity.
Not to mention the great effort MS makes at backward compatibility. If you created an app in 2006, chances are it'll work on the latest version of .NET without much trouble.
Nothing beats the integration level between .Net and VS, and I don't care what tech stack you're using to compare.
But outside of .Net, for things like C++, javascript, etc, things get a lot murkier.
Too many people obsess about backends. Yes, build your startup in C# and a .NET stack if that's what your familiar with. The backend ultimately doesn't matter, and the faster you can create and then iterate on your product, the better off you'll be. The primary factor that will decide whether your startup is successful or not is if people like your product and actually use it. None of your users will know or care what you built it in, be it .NET, RoR, Django, Yii, whatever.
The other person in my head is saying. "OH MY GOD NO". I've used the .NET stack and various OSS stacks to build complicated web applications. From this experience, I've concluded that the .NET stack sucks. Yes it works, but almost any OSS Framework will provide a much better developer experience. Better while developing the initial product, and better when maintaining and extending it.