4 ms·

This is a great way for Microsoft to show the potential of and build awareness for .NET core, I hope they are helping these guys. The nuget thing is inefficien

This is a great way for Microsoft to show the potential of and build awareness for .NET core, I hope they are helping these guys. The nuget thing is inefficient, MS should plot a path to make npm a first class citizen in all ms tools.

kevin_thibedeau 10y ago
That would require a filesystem that can handle node first.
mathw 10y ago
How is nuget less efficient than npm?
amcrouch 10y ago
Why on earth would MS want npm to replace what is one of the better parts of the .Net world?
amcrouch 10y ago
Why on earth would MS want npm to replace what is one of the better parts of the .Net world?
douche 10y ago
No, please, no. It'd be nice if somebody would get back to maintaining nuget packages for front-end stuff, the way it was a few years ago, before everyone collectively threw in the towel, shrugged, and said, "I guess npm isn't that painful. You know, compared to having forks shoved in my eyeballs, it's quite nice."
nvivo 10y ago
NPM is already supported by default for quite some time in VisualStudio.
WhitneyLand 10y ago
>NPM is already supported by default for quite some time in VisualStudio I should have been more clear. I mean MS should work with Node/LAMP people to invest in one package manager more than the other. Like they did with TypeScript, they didn't just build a tool that linux people never used, they made useful tooling and also spent a lot of time bringing Google and others into the fold. It makes sense to back npm because (guessing) it's used more than nu-get is used by VS devs. However if nu-get has a stronger ecosystem, stronger user base, etc choose it. Having competition is usually good, but sometimes it just means it's more work to have to learn more/work more to get the same thing done (if you work across environments). Take instant messaging protocols, lots of competition but not even having cooperation has made the result terrible. Incompatibility everywhere, reinventing the wheel, etc. To be sure some things are better not unified. We have multiple, un-unified browser engines and implementations which is critical. It improves competition, innovation and quality while still allowing surface level standardization in html/css/etc. I try to look at each set of competing projects independently and ask: Overall is this helping, or it is mostly just wasting time as clients are forced to learn multiple techs.

kevin_thibedeau 10y ago

That would require a filesystem that can handle node first.

mathw 10y ago

How is nuget less efficient than npm?

amcrouch 10y ago

Why on earth would MS want npm to replace what is one of the better parts of the .Net world?

amcrouch 10y ago

Why on earth would MS want npm to replace what is one of the better parts of the .Net world?

douche 10y ago

No, please, no. It'd be nice if somebody would get back to maintaining nuget packages for front-end stuff, the way it was a few years ago, before everyone collectively threw in the towel, shrugged, and said, "I guess npm isn't that painful. You know, compared to having forks shoved in my eyeballs, it's quite nice."

nvivo 10y ago

NPM is already supported by default for quite some time in VisualStudio.

WhitneyLand 10y ago

>NPM is already supported by default for quite some time in VisualStudio I should have been more clear. I mean MS should work with Node/LAMP people to invest in one package manager more than the other. Like they did with TypeScript, they didn't just build a tool that linux people never used, they made useful tooling and also spent a lot of time bringing Google and others into the fold. It makes sense to back npm because (guessing) it's used more than nu-get is used by VS devs. However if nu-get has a stronger ecosystem, stronger user base, etc choose it. Having competition is usually good, but sometimes it just means it's more work to have to learn more/work more to get the same thing done (if you work across environments). Take instant messaging protocols, lots of competition but not even having cooperation has made the result terrible. Incompatibility everywhere, reinventing the wheel, etc. To be sure some things are better not unified. We have multiple, un-unified browser engines and implementations which is critical. It improves competition, innovation and quality while still allowing surface level standardization in html/css/etc. I try to look at each set of competing projects independently and ask: Overall is this helping, or it is mostly just wasting time as clients are forced to learn multiple techs.