TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

The Future of NPM

12 点作者 dscape超过 11 年前

1 comment

ilaksh超过 11 年前
The nice thing is that there is a setting to specify where the location is if you prefer a certain implementation or host. Which I think is another example of how well designed npm is. My question is, is there a way to evolve the protocol a bit to be more practical for ensuring that multiple &quot;central&quot; registries are able to stay in sync? Or is the current system which is tied to Couchdb replication specifics (I think) the best way?<p>I agree with the general idea of separating out the concern of the metadata index from the actual hosting of the packages. I also agree that its important though to keep changes transparent and practical for people to implement on their own.<p>I can&#x27;t help but mention one more time how interesting these issues are in relation to what I see as an inevitable move from a fundamentally server oriented network architecture for the internet to a fundamentally distributed data oriented architecture. And that change presents many challenges including how it intersects with business interests.