Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NPM Is Joining GitHub

github.blog

Post reply on HN
Print view View original

181–190 of 588 posts

Re: NPM Is Joining GitHub

#181

Post by justinmeiners »

Nullabillity wrote: post #165
ethomson wrote: post #103

Earlier quoted context omitted.

Product Manager at GitHub here - I'll be the Product Manager for npm when the acquisition closes. I agree - npm is definitely an integral part of the JavaScript ecosystem. The npm package registry will remain free for public projects. We're going to work to ensure that the service is stable and accessible, and ready to serve the next million packages. This is independent of what Microsoft's doing with .NET Core. I'm…

> I'm excited about the work that they're doing Sounds like it won't be shielded from the cult-like MS mentality, then.

? This is regular PR speak.

Re: NPM Is Joining GitHub

#182

Post by tomnipotent »

fredsted wrote: post #83
banachtarski wrote: post #48

Earlier quoted context omitted.

I installed Windows Subsystem for Linux 2 on an older machine just now. The MSFT of today is definitely a far cry from the MSFT of yesteryear. Such a thing would have been unheard of 15 years ago.

Embrace, extend, extinguish?

Can you give any examples in the last 10-15 years?

Re: NPM Is Joining GitHub

#183

Post by wwweston »

flanbiscuit wrote: post #150

I wonder if more people will look into adopting Deno[1], the new node alternative by one of the creators of Node. It does not use NPM, you pull in packages Go-style (via URLs[2]). It's supposed to be more secure because you have to explicitly give it access to anything (i.e. network, file system, etc). [1] https://deno.land/ [2] example import in Deno: import { serve } from "https://deno.land/std@v0.36.0/http/server.…

The thought that's going into Deno about permissions and upstream package issues have me considering it where I've generally rejected node.js for anything serious (also recognizing that it's probably early for production use).

Re: NPM Is Joining GitHub

#184

Post by filoleg »

sneak wrote: post #146
bdcravens wrote: post #137

Earlier quoted context omitted.

Then you must not like React or Angular, since the owners of those projects are the largest spyware and aggregators of personal data in the history of humanity.

Software and services are not the same thing. For some examples: RMS being a douchebag has nothing to do with the usefulness of gdb, nor can that circumstance affect the utility in any imaginable scenario. Microsoft setting censorship policies (aka ToS) on a website they own and control directly affects the utility of npm/yarn/clients. Their website, their rules.

Well, this comparison seems to be close enough. What about VSCode and Github itself?

Re: NPM Is Joining GitHub

#185

Post by K0nserv »

sneak wrote: post #125
K0nserv wrote: post #14

This seems like a good outcome overall. NPM being such an important pillar in the software supply chain while having an unviable business model and largely being funded by VC money was never a good position to be in. There are problems with more of the software ecosystem consolidating with a single entity but it still feels like an improvement.

I do not consider the largest distributor of proprietary, closed-source spyware (Windows) owning the fastest growing open source package manager to be a good outcome, personally.

It depends on what the alternative is. When NPM starts running out of money to run the service what would happen? More VC, but only to a point and the firms would be increasingly be influencing NPM to make money by any means(probably not good for anyone but the firms). Alternatively a cash strapped NPM fails to invest in security and availability of the service leading to widespread outages or worse a large scale supply chain attack facilitated via the registry.

Re: NPM Is Joining GitHub

#187

Post by oever »

franciscop wrote: post #26

I'm surprised there's not a single mention of "Microsoft" in this or the npm announcement [1], given the old-evil-history of Microsoft and the new-nice Microsoft we have today. I would expect that there was at least a mention, considering the reason that most modules in npm are still in ES5 is exactly because of the monopolistic practices that Microsoft followed back in the day which makes Internet Explorer still rel…

Microsoft wants to host as much information as possible so it can collect data on developers and users. It is very hard to avoid giving data to Microsoft. GitHub, NPM, LinkedIn, Office 365, Teams, the lock-in is still alive.

A decentralized web or a non-for-profit like Wikipedia is a much better model for these infrastructure projects.

Re: NPM Is Joining GitHub

#188

Post by mundo »

franciscop wrote: post #26

I'm surprised there's not a single mention of "Microsoft" in this or the npm announcement [1], given the old-evil-history of Microsoft and the new-nice Microsoft we have today. I would expect that there was at least a mention, considering the reason that most modules in npm are still in ES5 is exactly because of the monopolistic practices that Microsoft followed back in the day which makes Internet Explorer still rel…

Yes, why is this not titled "Microsoft acquires npm"?

Re: NPM Is Joining GitHub

#189

Post by nixpulvis »

epicide wrote: post #154
nixpulvis wrote: post #138

Earlier quoted context omitted.

Sleez'n their way into our hearts. I can't say I really blame them, but god I hate it all.

What does a trustworthy Microsoft look like to you?

I don't really distrust Microsoft per se.

I just find it tragic that the only way GitHub could survive (I guess) was to be BOUGHT. Like why couldn't they stay smaller, focus on what they were good at, and standardize with the community all the integrations in an orderly manner?

Although, Microsoft has shown they care more about the developer community than Apple as of late. So for that, I can at least say my trust is rising. But it's a bit too late for me, I'm happily running Linux for most of my daily life.

Post reply on HN