Then don't write any code, because clearly you don't have enough belief that you (or I or whoever) can weigh the various tradeoffs to make the right decision.

Too often the decision masquerading as "best tool for the job" is in reality "the technology I'm fan of".

I really would not want to be the person, who few years since now is responsible for maintenance of some legacy Silverlight application. It is going to be exactly ugly as maintaing IE6 only application today. The difference is, that it is easier to avoid that now.

I really don't know what would make Silverlight best tool today (except for very specialized solutions). No, support in VS does not count.

Well then what would you use? HTML? That's what the guy who said to based their whole new system on Gopher said in 1992.

It's a stupid argument. I mean really a STUPID argument to say "don't use the best tools, use the tools that some random guy on HN says to use". If you can't trust your own judgment I'd quit software development right now. You really just have no business writing code. Because if you can't pick the best tools based on info, how can you pick the right architecture, or pattern, or prioritize which bugs to fix, or which scenarios to support, or which person to marry or when to have kids or when to buy a house.

I hate to be so blunt, but this reminds me of religious zealots who say, "ignore your best evidence... just trust us". Anyone who goes down that path simply has lost all of my respect.

And yes, downvote away. I just have trouble believe someone on a hacking site would say, "don't do what you think is best based on your own due diligence... follow some arbitrary crowd".