I agree. I think whichever stack you pick will be the "wrong" one for some people, anyway :). What matters is bringing something useful and usable right up front, because if you even can't do that, then it doesn't matter which stack you pick, you'll never get off the ground. I'd suggest picking the one you're most comfortable with, that helps you get things done instead of getting in your way. Once you've proved a concept and gained a bit of feedback and traction, then you can start looking at other stuff, if that's even necessary.
(Full disclosure: I build things using both ASP.NET MVC and node.js: they both have their strengths, and both have their weaknesses). Which one is "best"? IMO, it depends on the context, and what you're trying to do.
(Full disclosure: I build things using both ASP.NET MVC and node.js: they both have their strengths, and both have their weaknesses). Which one is "best"? IMO, it depends on the context, and what you're trying to do.