I mostly agree, I’ve been a .net developer for over a decade and the current state of things is very wonky. For the past couple years I’ve been unsure where to

I mostly agree, I’ve been a .net developer for over a decade and the current state of things is very wonky. For the past couple years I’ve been unsure where to focus my efforts to make sure I don’t wind up in another situation where I get very good at Silverlight just to have it all thrown away. At this point with Microsoft half backing away from UWP and half continuing to push it, I don’t know if it’s better for me to make the jump or not. Also it’s more clear now that .net Core the future, but for a while it’s been very confusing and it’s still not 100% clear if it’s going to encompass all the scenarios I need or if I’m going to have to keep abreast of both sides. Rather than staying at the bleeding edge of .net like I used to, I’ve been finding it safer to just give it space and wait for things to solidify. All in all, developing for the Microsoft platform has become very confusing over the past several years. Still better than trying to keep up to date on the NodeJS or frontend development world though :-P