Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NPM: 429 Too Many Requests

github.com

Post reply on HN
Print view View original

41–50 of 171 posts

Re: NPM: 429 Too Many Requests

#41

Post by swalsh »

gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

Most companies try to stay professional, and many people carry that behavior into github. However I have worked at a major tech company that trended closer to "millenial" in age. There memes were an everyday part of the corporate culture. Professional emails quite often would have a meme included. I can see someone coming from a corporate culture like that thinking it would be perfectly normal to carry this behavior into a public github issue like this.

Re: NPM: 429 Too Many Requests

#42

Post by chrissnell »

I dealt with this problem at a previous job where we had a build pipeline and apps that were very dependent on NPM. To fix it, I used nginx to build a set of two-tiered caching servers within our CI Kubernetes cluster. One used a ramdisk to provide a low latency cache for the NPM client fetches. The second was a disk-backed cache to provide persistence to the ramdisk-backed cache. I had a script that would alter the package deps so that they were pulled from the ramdisk-backed service, which used the disk-backed service as it's backend. The disk-backed service uses actual NPM URLs for its backend.

The result was lightning-fast fetches and no rate limiting.

We needed the two-tiered system because this was Kube and occasionally we would have to rebuild/restart nodes and we didn't want to completely lose the cache when that happened.

You can easily extend this system to handle any package artifacts used in your build process: .deb's, .rpm's, etc.

Re: NPM: 429 Too Many Requests

#43

Post by dajonker »

gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

From the outside, it seems like Javascript developers are all in high school, participating in a popularity contest, feel the need to sprinkle emoji everywhere and communicate solely with memes and gifs.

Re: NPM: 429 Too Many Requests

#44

Post by jtdev »

lm28469 wrote: post #10
gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

Some people getting in the workforce in the last few years have troubles making the distinction between work and play contexts. It's extremely visible on github, slack, &c. which are more and more looking like discord / reddit (gifs, memes, random jokes in the middle of serious discussions)

In my observation, this demographic is most densely concentrated in the JavaScript community. Not sure what that says about the language itself, but there’s definitely a glut of unprofessional JS devs out there.

Re: NPM: 429 Too Many Requests

#45

Post by aosaigh »

gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

It's embarrasing. I think posting memes like this is an easy way for people to feel creative and edgy while being nothing of the sort.

Re: NPM: 429 Too Many Requests

#46

Post by Hamuko »

MattRix wrote: post #36
lm28469 wrote: post #10

Earlier quoted context omitted.

Some people getting in the workforce in the last few years have troubles making the distinction between work and play contexts. It's extremely visible on github, slack, &c. which are more and more looking like discord / reddit (gifs, memes, random jokes in the middle of serious discussions)

This is the first time I've seen "&c" used instead of "etc", I had to look it up. Interesting abbreviation!

Why would anyone use "&c" considering that it doesn't actually save any key presses?

Re: NPM: 429 Too Many Requests

#47

Post by SirensOfTitan »

I’ve been considering checking node_modules into source control for some time now, has anyone else done that successfully? There would be a variety of benefits:

1. Eliminate redownload of packages on every CI build 2. Reduce the amount of gigantic IO operations from unpacking the tens-of-thousands of files sitting in node_modules. 3. Better security: code checked in can be audited better if not downloaded every single CI build.

yarn’s PnP system is promising for the zero-install paradigm, but it doesn’t seem quite ready yet (so many packages don’t seem to get their dependencies right).

Re: NPM: 429 Too Many Requests

#48

Post by easytiger »

matsemann wrote: post #14
lm28469 wrote: post #10

Earlier quoted context omitted.

Some people getting in the workforce in the last few years have troubles making the distinction between work and play contexts. It's extremely visible on github, slack, &c. which are more and more looking like discord / reddit (gifs, memes, random jokes in the middle of serious discussions)

You say it like it's a bad thing? It's possible to be both professional and have some fun (not talking about the linked GH).

I mean there is a difference between having fun and conducting yourself in a professional manner where appropriate.

With the increase in adoption of certain technologies (node etc) I have noticed a relationship with the people employed to work with them and their poor level of professionalism in the workplace with regard to their work and how they deal with other people (in the UK) and even how they dress. Similar age groups in other areas don't display these traits.

A number of these people work as contractors as well, so at least it was easy to get rid of them.

Go post memes on the LKML and see what happens

Re: NPM: 429 Too Many Requests

#50

Post by [deleted] »

hans1729 wrote: post #27
matsemann wrote: post #14

Earlier quoted context omitted.

You say it like it's a bad thing? It's possible to be both professional and have some fun (not talking about the linked GH).

Having fun is not whats discouraged. Rather: if I'm looking for the solution for some problem, I don't want to scroll through memes, because I want to be productive, getting things done. Spam/fog in the resolution-thread obviously doesn't help with that; the opposite is the case.

[deleted]
Post reply on HN