IF you, as a technical lead, are building a product which is shipping in 2016 and decide to build it on something like .Net Core then you DESERVE to get sacked.

IF you, as a technical lead, are building a product which is shipping in 2016 and decide to build it on something like .Net Core then you DESERVE to get sacked. You're a leader, you are responsible for doing the risk assessment. Do you build your product on a platform which is been in development for 18 months; which is an ambitious rewrite, and which is planned to have the first RTM in the second half of the year? You're lying to yourself if you say that you're working in the best interests of your employers if you say yes. You're being irresponsible. You're doing CV-driven-development. As a leader you're an experienced developer: you know that shipping dates are unreliable at best. We know that version 1 of anything is simply a starting point. You know that building a platform is extremely risky. This is exactly why I chose not to immediately start using .Net Core. Sure, the tech is great, but it is bound to be delayed. No way am I betting 6-9 months of a team of 10 developers on that.