3 ms·

Microsoft will frequently hype up things only to drop them 1-2-3 years later. Beware of the hype, especially when coming from MS. Also, keep stuff up-to-date,

Microsoft will frequently hype up things only to drop them 1-2-3 years later. Beware of the hype, especially when coming from MS. Also, keep stuff up-to-date, MS will at the same time maintain things forever and drop them mercilessly (look at .NET framework itself; it still runs - so counts as "maintained"; but if you didn't migrate to .NET core/ .NET5 / .NET6, you're in a very bad position for the future. With the announcement of .NET core they made a lot of code obsolete). The previous two things combined create a somewhat bizarre situation: you want to keep up to date with the latest things MS is up to.... but not TOO up-to-date, because you can get into the "hype that will be killed" train. E.g. .NET core 1 was too early to jump onboard - wasn't clear that it's not going to be an UWP. But by .NET core 3, you'd better pay close attention and be ready to invest whatever it takes to move on to the new tech. Probably around .NET core 2.1 was the moment when one should've confidently said that "MS is serious about this .NET core stuff"? (though the exact timing is of course debateable)

EVa5I7bHFq9mnYK 5y ago
>> Microsoft will frequently hype up things only to drop them 1-2-3 years later. Same as Google. Same as YC :)
Salgat 5y ago
.NET Framework was actively developed for two decades. It's not a jab at them to finally move on to a new runtime while simultaneously providing a very excellent migration path. And all the things Microsoft "hypes up them drops after a few years" have low adoption compared to their main offerings anyways. It would be silly of them to continue actively developing things like Silverlight when everyone saw that better options were available.
- virgilp 5y ago
  It makes perfect sense to do what they do! And in all honesty sometimes they grind for a very long time before achieving true success (see: Xbox). That said, people don't always realize how many things Microsoft tries (and subsequently abandons, because of course not all of them are going to be a success). That .net core was a success is clear now; but you could've easily believed that UWP will be a success and invested in it (in fact, I know teams who did, with really bad consequences for them). What I say is... just wait a bit. In the early days, not even Microsoft knows what will succeed, and they will "sell" their new initiatives very hard (of course!).

EVa5I7bHFq9mnYK 5y ago

>> Microsoft will frequently hype up things only to drop them 1-2-3 years later. Same as Google. Same as YC :)

Salgat 5y ago

.NET Framework was actively developed for two decades. It's not a jab at them to finally move on to a new runtime while simultaneously providing a very excellent migration path. And all the things Microsoft "hypes up them drops after a few years" have low adoption compared to their main offerings anyways. It would be silly of them to continue actively developing things like Silverlight when everyone saw that better options were available.

virgilp 5y ago
It makes perfect sense to do what they do! And in all honesty sometimes they grind for a very long time before achieving true success (see: Xbox). That said, people don't always realize how many things Microsoft tries (and subsequently abandons, because of course not all of them are going to be a success). That .net core was a success is clear now; but you could've easily believed that UWP will be a success and invested in it (in fact, I know teams who did, with really bad consequences for them). What I say is... just wait a bit. In the early days, not even Microsoft knows what will succeed, and they will "sell" their new initiatives very hard (of course!).