4 ms·

The old perception of .NET devs is that they're provincial in their approach to tech outside of Microsoft. Stacks are always top to bottom straight from MSDN o

by libria 11y ago

The old perception of .NET devs is that they're provincial in their approach to tech outside of Microsoft. Stacks are always top to bottom straight from MSDN or P&P: jQuery, razor, ASP.NET MVC, WCF, EF, MSSQL, TFS. Part of this is MS fault: the silver/gold partner licenses provide financial incentive for businesses to stay in the fold by being MS stack proficient. I've seen Biztalk shoe-horned into a product mostly because it was included in the quarterly MSDN mailout CD package and hey, it's free! To some degree, it's true. Many of my colleagues never touched node.js til Microsoft started using it. Or Linux til Azure supported it. Or functional programming til F#, or git etc. Java developers seem more comfortable searching online and piecing together a solution from oracle, apache common, other 3rd parties. It feels like they're better at critically inspecting packages for performance, applicability, adoption since they don't have a mother corp creating or blessing every product. nuget has helped a lot of .NET devs come out of their cave and explore the great unknown that is open source. Hopefully Microsoft's recent reinvention of itself changes both this perception of .NET devs and whatever reality is behind it.

wolfgke 11y ago
> Many of my colleagues never touched node.js til Microsoft started using it. Couldn't there also be the reason that before Microsoft started to become active in Node.js the Windows support for it was really bad (bad Windows support is a typical problem of lots of open source projects; I mean: I could understand it if OS X (at least the same degree proprietary) support were similarly bad, but this is usually not the case).
- ihsw 11y ago
  Node is very attractive for a variety of reasons, and TypeScript complements it like hand in glove (which is completely intentional, kudos to MS on that part). Transitioning to Node+TS from .Net is fairly straightforward (setting aside the completely new tooling, building, open source package resources, etc), and you get microservices + much better performance with minimal friction. Granted, large-scale systems of the Node variety are a world's difference from .Net, but that is not insurmountable. The appeal is more than simply improving compatibility -- the whole microservices movement had been happening beneath Microsoft's noses, and this is their response to it. It is nothing short of impressive how they have expanded the .Net stack in order to remain current.

by libria 11y ago

wolfgke 11y ago

> Many of my colleagues never touched node.js til Microsoft started using it. Couldn't there also be the reason that before Microsoft started to become active in Node.js the Windows support for it was really bad (bad Windows support is a typical problem of lots of open source projects; I mean: I could understand it if OS X (at least the same degree proprietary) support were similarly bad, but this is usually not the case).

ihsw 11y ago
Node is very attractive for a variety of reasons, and TypeScript complements it like hand in glove (which is completely intentional, kudos to MS on that part). Transitioning to Node+TS from .Net is fairly straightforward (setting aside the completely new tooling, building, open source package resources, etc), and you get microservices + much better performance with minimal friction. Granted, large-scale systems of the Node variety are a world's difference from .Net, but that is not insurmountable. The appeal is more than simply improving compatibility -- the whole microservices movement had been happening beneath Microsoft's noses, and this is their response to it. It is nothing short of impressive how they have expanded the .Net stack in order to remain current.