3 ms·

I found myself in a similar situation back in 2011. The .NET ecosystem went stagnant as resources were shifted towards the upcoming Windows 8 release, and that

by rl3 10y ago

I found myself in a similar situation back in 2011. The .NET ecosystem went stagnant as resources were shifted towards the upcoming Windows 8 release, and that in turn made everything weird. That weirdness continues today in the form of UWP. I'm glad I extricated myself from their ecosystem when I did. As much as I loved C# and wanted Microsoft to succeed, it felt very much like being on board a sinking ship.

da02 10y ago
What ecosystem do you work on and use today?
- tracker1 10y ago
  Can't speak for GP, but jumped over to Node myself near that time... spent a few years migrating .Net apps, and today mostly work in Node. I've enjoyed it a lot, despite some recent pain (going from Webpack 1 and nyc/mocha/chai to Webpack 2 and Jest) it's still been nicer than when I have to fire up VS (in a VM even) to help with a bug at work. I will say the .net core stuff is looking really nice to work with though.
- rl3 10y ago
  Anything that isn't Microsoft, with the exception of Typescript. Primarily the Node/NPM ecosystem though. .NET Core is looking nice, but I'd rather not risk being burned twice.
  - narrator 10y ago
    Typescript is supported by Google in Angular2, so it's not a completely Microsoft dominated effort. It's also just a transpiler so it doesn't call into a bunch of closed source Windows APIs which might not work quite right when implemented on non-MS platforms.