Whenever Microsoft gets involved in the open source world it tends to cause some observers to challenge the software giant's motives. GitHub's NPM acquisition this week served up fear of the Micros...

It would be an overstatement to say Microsoft now has an iron grip on JavaScript, a view that is rooted in fear among those who remember the time when Microsoft was openly hostile to open source, Murphy added.

“How you package for Node.js is hardly controlling the future of JavaScript,” he said. “Microsoft does have a large play in JavaScript as a whole, but it is an open community.”


How you package for Node.js is hardly controlling the future of JavaScript

Maybe not, but it’s still a very substantial part of the JavaScript ecosystem as a whole.

I’ve always been scared of this whole NPM thing in general. Microsoft are scooping up a lot of the companies behind the JavaScript ecosystem. I think at this point we have to realise that Node.js was doomed from the start: why is NPM a centralised, private closed-source registry which comes with Node.js by default? Can anyone else see the issue here?

Deno seems like a good initative. Good package management (it doesn’t exist), no centralised registry, no closed-source bullshit. It’s such a breath of fresh air.

The JavaScript community in Lemmy

    A community about JavaScript, the ECMAScript standard, and programs that make use of JS such as Node.js.

    • 0 users online
    • 1 user / day
    • 2 users / week
    • 2 users / month
    • 7 users / 6 months
    • 302 subscribers
    • 44 Posts
    • Modlog