Nicholas Zakas

But just off the top of my head, how many read replicas that you need and where you need them?

What sort of traffic are you getting from publishing and how frequently?

And how do you cache effectively to make sure that CI systems are up to date and also not unstable?

There's a lot that goes into managing the registry.

I would say, you know, it's probably kind of similar to like running YouTube in a way.

Because YouTube, before they got bought by Google, like this was also a problem of just like managing the scale that was going on.

And part of why Google was an ideal destination for YouTube was they had the infrastructure and the operational knowledge in order to keep that site up and running, even with all of the traffic and all the bandwidth that it had.

eats up every day um and again if you look at claude like how frequently does claude go down um because they run into like bandwidth issues like it still is more frequently than you'd like to admit um they're getting better but like it still happens

I don't personally.

I think that for a registry to have a chance to compete with NPM, I think it has to come from a company or a person starting a company that is already trusted by the community.

And that's why I thought

JSR had a real shot.

Because coming out of Deno, coming from Ryan Dahl, already had a lot of trust in the community and always presenting himself as wanting to do the right thing for the JavaScript ecosystem.

I thought JSR really had that shot.

And to see it kind of fade away has been really disappointing.

Yeah, I think that's exactly it.

I think it's a scaling problem because there are package managers around before NPM existed.

and RubyGems.

So crates came around afterwards and was kind of inspired by NPM, but they don't have anywhere near the scale.

Yeah, I don't know that much about the Python ecosystem.