4 ms·
> Certainly, Microsoft has, can, and will drop the ball, but they also have a very long track record available to build [dis]trust upon Your post seems a bit s
by hn_throwaway_99 5y ago
> Certainly, Microsoft has, can, and will drop the ball, but they also have a very long track record available to build [dis]trust upon
Your post seems a bit strange given that Microsoft is the company that let any package owner publish any other NPM package.
- datenarsch 5y agoDon't try to put the blame for the absolute mess that is NPM on Microsoft.
- detaro 5y agoMicrosoft wanted to own it, so now they own it. If they buy stuff they can't fix, their problem.
- hn_throwaway_99 5y agoMS bought NPM in March 2020. I'm certainly not "blaming" MS for NPM's issues, but they bought them, so they're definitely responsible for them now.
- deleted 5y ago[deleted]
- bob1029 5y agoI realize it looks like an odd contradiction, but doing highly-effective business on top of Microsoft products is sometimes a game of compromises and grey areas. Even though Microsoft is ultimately responsible for NPM on the org chart, I still dont mind the entire ordeal from my current perspective. No one ever said we had to use 100% of Microsoft's product offerings. The nuance is in selective adoption and careful negotiation of roadmaps. I will signal my displeasure with Microsoft's acquisition of the NPM ecosystem by simply disregarding it's existence and never electing the node workload at VS install time. That's all it really takes to entirely opt-out for us. I don't hold any principled grudges against an organization larger than most municipalities. There are a lot of stakeholders involved here.