21–30 of 83 posts
Privately run 'open source' code repositories are not what the open web should run on. I would say that this marks the beginning of the end for npm as anything viable for front-end code repositories and probably for anything related to node. I propose an open-source alternative for front-end JavaScript libraries and dependency management. Anyone calling for npm modules and browserify to rule the day for front-end JS…
Per his blog, Fast.ly is now hosting the npm registry, so the money is not going for hosting. It's to build some kind of sellout business. Back in July he must've seen this coming because he switched the npm license from MIT to the more restrictive Artistic 2.0: https://github.com/npm/npm/commit/c32391b1efd70a861cebc77e0c... He's already taken away the download numbers on npmjs.org, so maybe he intends to sell the "a…
Per his blog, Fast.ly is now hosting the npm registry, so the money is not going for hosting. It's to build some kind of sellout business. Back in July he must've seen this coming because he switched the npm license from MIT to the more restrictive Artistic 2.0: https://github.com/npm/npm/commit/c32391b1efd70a861cebc77e0c... He's already taken away the download numbers on npmjs.org, so maybe he intends to sell the "a…
As of five days ago ( http://blog.npmjs.org/post/75707294465/new-npm-registry-arch... ) we are hosting the registry ourselves; it was previously hosted by Nodejitsu (who still operate a downstream mirror).
As for the download counts, per Twitter ( https://twitter.com/npmjs/status/422823647619710976 ), we removed the download counts because our original solution for those counts (keeping them in CouchDB) wasn't scaling. I am literally, as we speak, working on the replacement system to restore download counts.
And Isaac's LinkedIn title is a joke. I hope that's obvious.
Per his blog, Fast.ly is now hosting the npm registry, so the money is not going for hosting. It's to build some kind of sellout business. Back in July he must've seen this coming because he switched the npm license from MIT to the more restrictive Artistic 2.0: https://github.com/npm/npm/commit/c32391b1efd70a861cebc77e0c... He's already taken away the download numbers on npmjs.org, so maybe he intends to sell the "a…
It's not accurate to say that Fastly is hosting the registry; Fastly are providing CDN services to our registry -- a globally distributed cache -- for which we're very grateful. As of five days ago ( http://blog.npmjs.org/post/75707294465/new-npm-registry-arch... ) we are hosting the registry ourselves; it was previously hosted by Nodejitsu (who still operate a downstream mirror). As for the download counts, per Twit…
One thing I'm a tad annoyed by - this deal was being put together simultaneously with the "scalenpm" crowdfunding drive. A shoutout to the supporters of that drive would have been nice...
Earlier quoted context omitted.
It's not accurate to say that Fastly is hosting the registry; Fastly are providing CDN services to our registry -- a globally distributed cache -- for which we're very grateful. As of five days ago ( http://blog.npmjs.org/post/75707294465/new-npm-registry-arch... ) we are hosting the registry ourselves; it was previously hosted by Nodejitsu (who still operate a downstream mirror). As for the download counts, per Twit…
Thanks for clearing it up. I knew there are technical/logical answers to all of the points people are bringing up.
Per his blog, Fast.ly is now hosting the npm registry, so the money is not going for hosting. It's to build some kind of sellout business. Back in July he must've seen this coming because he switched the npm license from MIT to the more restrictive Artistic 2.0: https://github.com/npm/npm/commit/c32391b1efd70a861cebc77e0c... He's already taken away the download numbers on npmjs.org, so maybe he intends to sell the "a…
It's not accurate to say that Fastly is hosting the registry; Fastly are providing CDN services to our registry -- a globally distributed cache -- for which we're very grateful. As of five days ago ( http://blog.npmjs.org/post/75707294465/new-npm-registry-arch... ) we are hosting the registry ourselves; it was previously hosted by Nodejitsu (who still operate a downstream mirror). As for the download counts, per Twit…
i understand someone has to pay for the servers and development time, but would it be possible to give a hint for the types of things you plan to charge for? Even just a rough sketch of "we will offer private repositories" or "we will offer support." I appreciate the "reassurances" that nothing will change today for me, but the ambiguity prevents my latent paranoia from going away.
And now izs starts a new company npm inc. that will, well, who knows. But he's former Joyent who power npm, so will running npm transfer to npm inc.? But how does Nodejitsu or the 300K that they raised with their campaign fit into this picture?