NPM Is Joining GitHub
151–160 of 588 posts
Re: NPM Is Joining GitHub
#152I occasionally forget that Microsoft bought GitHub. They certainly don't do anything here to remind me of that fact. How separate from MS has GitHub been in day-to-day operations?
I've been at GitHub for 7 years and we operate independently but have the support and resources of Microsoft when we need them. IMO, they've been amazing partners but day to day the GitHub team builds, prioritizes, and supports GitHub.
This is as good as Google acquiring Youtube because Youtube needs an insane amount bandwidth and it was a perfect fit for Google's infrastructure and ad platform.
It's just sad to see Google not playing the Developers game well.
Re: NPM Is Joining GitHub
#153I wonder to what extent they've had influence over their own success at all though. Basically they had to hope that JS stayed popular (it did), that Node stayed relevant (it did) and that the entire JS ecosystem would move over to NPM (it did, but I'd say rather despite NPM than because of it) (I mean, otherwise Yarn wouldn't even exist, right?).
So basically their bet was:
- Turn NPM into a startup
- Keep the lights on
I bet I'm missing all kinds of key behind-the-scenes stuff, but still, I don't know many startups that manange to successfully exit by "just" keeping the lights on. In a weird cringey way, it's motivating.
Re: NPM Is Joining GitHub
#154Earlier quoted context omitted.
Microsoft is aware of their reputation. So much that they even have a policy of not allowing Microsoft+Github co-brand promotions. They want the Github brand to stay strong instead of being diluted into some mix of Github and Microsoft.
Sleez'n their way into our hearts. I can't say I really blame them, but god I hate it all.
Re: NPM Is Joining GitHub
#155Earlier quoted context omitted.
Yes, they almost own the entire JS ecosystem at this point. They lost a decade of battles for the web, but it seems they just found a way to get back in the fight. Now at the IE 6 times, that meant monopoly, and it was terrible news. But today, it means more competition between the giants, which is very good for us.
One could argue that the IE6 of our times is Google Chrome at this point..
Re: NPM Is Joining GitHub
#156Earlier quoted context omitted.
My understanding was that financially they were not going to last long doing what they were doing.
That raises the question of how GitHub/Microsoft plan to profit off the acquisition though? It can't be just for goodwill or marketing.
Re: NPM Is Joining GitHub
#157(Wishful thinking ...) Does this mean the next release of npm will be yarn v2 and that typescript will implement support for the pnp spec so we can converge the javascript packaging space to a sane place?
Re: NPM Is Joining GitHub
#158Earlier quoted context omitted.
Embrace, extend, extinguish?
My prediction, that my IT department hates to hear, is that Windows is going away. Microsoft doesn't want to be Microsoft anymore; it wants to be Oracle and IBM and primarily make money off of business consulting and the cloud. I think Windows will eventually become a presentation and slowly-phased-out compatibility layer on top of Linux, similar to the way macOS became Unix, but even less different than its underlyi…
I think this is unlikely. In many ways the NT kernel is superior to the Linux kernel. I just wish it were open source and didn't have the rest of windows around it.
Re: NPM Is Joining GitHub
#159Earlier quoted context omitted.
You aren't the only one. Most users are too young to understand how predatory Microsoft has always been. Can't wait for the "npm won't publish my package because it circumvents something in Windows" or whatever. Give it time.
Tbf Microsoft have won back a lot of good faith with developers due to projects like VS Code and TypeScript, even for those of us who remember their past. And we're yet to hear of any negative impact of their Github acquisition (afaik - correct me if wrong).