Nice People Matter? NPM may stand for Not Politely Managed – job cuts leave staff sore NPM, Inc, the company behind the widely used NPM JavaScript package repository, stands for Node Package Manager. Inside the small but vital biz, the name gave rise to an alternative de-abbreviation, Nice People Matter – but that might be about to change. For those who don't know, NPM is the default package manager for the …
How one developer just broke Node, Babel and thousands of projects in 11 lines of JavaScript
Code pulled from NPM – which everyone was using
"I think was a great disturbance in NPM, as if millions of Stack Overflow copypasters cried out in terror as their remotely hosted scripts were suddenly deleted."
And then security and reliability go up at least ten fold when they fix and self-host.
Because big $$$ is not made by individual subscribers... no sir, like Github, they want to make this by spinning out self-hosted or private services with SLA's to big companies, where they can charge 1000x the price (I kid you not!). But "Enterprise" level apps require a whole suite of additional features, including multiple authentication mechanisms, access logging etc.
Every company needs more management and marketing. You can never have too many HR bods either.
Quite, it's the corporate equivalent of hiring more security. A company goes to far along that road (and it's a short drive these days) and it's the corporate equivalent to the Ministries for Peace, Plenty and Truth.
HPE and the Truth Squad is a good example, but they are so far down the road, they've parked up alongside the rundown 1920's farm of the crazies.
"Why? They've got a very unique product already, if they don't fumble it by firing all the developers."
Because VC's invested US$10.6m in NPM and are looking to make money from their investment.
Can NPM support concurrent models (i.e. free/enterprise)?
Apart from providing a convenient place for others to host their javascript, does npm provide much at all? i.e. CPAN etc
Quite difficult. Linux and Apache's costs don't grow with usage, so a yearly donation from big companies can sustain their development. NPM's costs grow with every user, so the more they grow, the more donations they would need, and they can't even control the cadence at which they need that money.
Maybe if Javascript is important for anything it shouldn't be dependent on a small company
It isn't. It is entirely possible to use Javascript1 without using NPM. Reliance on a single-point-of-failure package manager is entirely a developer or organizational choice.
1Which should actually be ECMA... oh, forget it.
@John70
How do they handle the licensing in that enfironment? Does every developer need to understand the licensing of every component? The idea behind a centrally managed repositiory is that it provides understandable usage criteria - the language as a whole is covered, not the individual components.
As an aside, would you contribute for nothing to the development of NPM Big Corp Inc. when it is run by scrubs?
This post has been deleted by its author
I could write a package manager myself in less than a week. If one hosted it on something like AWS it could dynamically scale according to demand. What are these 55 people at NPM doing FFS? It's a *package manager*, not Google Docs.
WTF?
There should be two devs working on this, max. If they split the $3 million between them that's a nice little number they've got going.
It doesn't need to, and shouldn't be, some bullshitty glossy American corporate vehicle of evil. Bah.
"I could write a package manager myself in less than a week. If one hosted it on something like AWS it could dynamically scale according to demand. What are these 55 people at NPM doing FFS? It's a *package manager*, not Google Docs."
Go on then, write an alternative. That way even if you only take half their business, you still have the chance of trousering $1m for a week's work.
I can't for the life of me see why everyone doesn't try this....
VCs buy on profit potential. A company can spend years developing its people and good practices, getting a great reputation (and profitability) along the way which will get noticed. When the VC sees the potential and smells the profit, they swoop and strip back expenditure to make it lean enough to sell on or float, riding on the wave of the previous good name in the industry and the artificially healthy bottom line. Increasing profitability includes ramping up prices to where the analysts think they should be (regardless of existing market and sentiment), often re-branding at (wasted) expense to pitch at the bigger players and identifying "synergies" or "optimisation", or what the rest of us call redundancies.
As you can tell I'm still a bit bruised from the last portfolio company I was at.
Isaac Schlueter of npm, Inc. on hiring a CEO, in Founders Talk #61:
"And I have to really trust that he’s not gonna screw it up. It’s my baby, and you’re hiring somebody else to be your baby’s new parent."
"If I hire somebody else, they might not be good, the team might reject them, we might have this massive upheaval…"
Looks like Bryan Bogensberger is a pretty mobile guy, the sort who does facilitation and "strategic partnerships" for company after company, a few years here, a few years there.
His last gig, Quiver Media, are all about "communications".
Just the sort of guy to make engineers polish up their resumes.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
