Earlier quoted context omitted.
Hey Microsoft, if you're listening, you should throw Sonatype or other Maven-related organizations a few bucks. They deserve it.
Just because Microsoft has a lot of money doesn't mean they can just throw it around. That's not how the world works...
GitHub Package Registry
151–160 of 389 posts
Re: GitHub Package Registry
#152There's something slightly concerning about ceding responsibility for distributing the world's open-source projects from a family of strong independent repositories to a centralized platform owned by a tech giant.
Yes, but that's not a new concern - to some, GitHub has always represented an anathema to what git was supposed to be and bring. Centralization at a proprietary vendor, instead of open systems interacting. Then locking people in further by network effect and adding centralized products around git. That it's become so popular many people equate GitHub with git adds insult to injury. I completely understand why this al…
Re: GitHub Package Registry
#153Earlier quoted context omitted.
It is still really unorganized in many ways. The worst thing, I think, is search results still frequently list obsolete MSDN pages higher...and, btw, the new branding is not MSDN, but docs.microsoft.com. They still have a long ways to go, with the typical problems of a large organization tackling a large, kind of amorphous, project.
docs.microsoft.com PM here - thanks for the feedback! It takes some time to update all our search results across the two major search engines. Given that some pages have less traction than others, the more obscure content sometimes still is indexed as if it's coming from MSDN. We have moved most of the library to docs, with redirects in place, so hopefully you won't get too many 404s. If you do - feel free to report…
Re: GitHub Package Registry
#154Earlier quoted context omitted.
Hey Microsoft, if you're listening, you should throw Sonatype or other Maven-related organizations a few bucks. They deserve it.
Just because Microsoft has a lot of money doesn't mean they can just throw it around. That's not how the world works...
Re: GitHub Package Registry
#155... looking forward to the Hacker News post in 4 years about how Github has really lost their way and how they're now super evil. Remember this when you guys all rush to sign up for their new services because it's easier for you now ;)
Re: GitHub Package Registry
#156visual" rel="nofollow">http://www.visualstudioprofessionalpromocode.com">visual studio promo code office" rel="nofollow">http://www.office2019promocode.com">office 2019 promo code vmware" rel="nofollow">http://www.vmwarefusionpromocode.net">vmware promo code microsoft" rel="nofollow">http://www.micropromocodes.com">microsoft store promo code
Re: GitHub Package Registry
#157Re: GitHub Package Registry
#158Re: GitHub Package Registry
#159This is pretty interesting. Github really is becoming the social network that MS never seemed to be able to create. We already use it as our portfolio of work for potential employers. We collaborate with fellow enthusiasts and maybe even make new friends. We host our websites from it. Abuse it to store binaries, too. And now, along side, source code we can use it as a CDN of sorts to serve packages, for free, sounds…
It's the social network for... function Ballmer() { while (true) { print("Developers!"); } }
Re: GitHub Package Registry
#160I worry about npm now. The huge public registry everyone loves is run off investor's money and subsidized by npm's private registry product. But npm has recently changed their nice-people-matter CEO to a now-print-money dude, so I suspect investors' patience has run out. And now GitHub went directly after the one thing that npm is supposed to be making money on.