Live data from Hacker News

NPM: 429 Too Many Requests

github.com

101–110 of 171 posts

Re: NPM: 429 Too Many Requests

#101
post #87
post #34

Earlier quoted context omitted.

>It [...] discourages genuinely useful discussion of workarounds or progress. Does it though? Sounds like an opinion.

> Does it though? Sounds like an opinion. Given that the comments in question add absolutely no value to the issue and instead insert a bunch of visual noise and fog then I'd argue it's not an opinion.

>absolutely no value

This is the opinion part.

Re: NPM: 429 Too Many Requests

#102
post #44

Earlier quoted context omitted.

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.

I really think it’s just because it is the most popular and accessible language to the masses we get a larger sample of the population.

I think there's also more demand for JavaScript devs than other languages, and consequently there are more junior developers writing JavaScript.

Re: NPM: 429 Too Many Requests

#103

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).

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 ag…

> [..] and even how they dress.

While there are many points in your post that I agree with, we really should stop worrying about how people dress.

If it's a developer sitting behind a computer screen all day long with zero customer contact whatsoever, he really shouldn't be forced to wear a certain dress code just to satisfy someone's standard of professionalism. Such feelings are in similar spirit as "woman should not wear trousers" a few decades ago - there is just no rationale behind it other than conditioning by society.

Re: NPM: 429 Too Many Requests

#104

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).

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 ag…

I work badly with people that pronounce professionalism as a form of conduct too much to be honest. That said, my professional conduct on the technical side is always to vendor that shit if the project is of a nature that allows doing so (mostly restricted to proprietary software). Even for builds. There are harsh disadvantages with doing that if maintenance is disregarded, but these are problems you can tackle yourself instead of being dependent on third party tools working.

The sheer numbers of users of NPM says that this can happen from time to time and the stability they are providing is nothing other than exceptional.

Otherwise professional conduct mainly comes down to creating an atmosphere of noncommittal distance to deal with difficult personalities. I think being subjected to it for too long should disintegrate any personality, because it is completely unnatural. Hard to imagine people longing for more of that.

Re: NPM: 429 Too Many Requests

#105
post #65
post #41

Earlier quoted context omitted.

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…

I do not get this. My first job was at a company which had very unprofessional communication internally (for good and bad) but we always made a clear distinction between internal and external communication. There is a time and place for everything.

Perhaps our business is a part of it, we were a B2C company, and our communications with customers attempted to tend towards "cool and fun".

*FYI, I did not work at GrubHub, which probably fails the most at pretending to be cool and fun.

Re: NPM: 429 Too Many Requests

#106
post #46
post #36

Earlier quoted context omitted.

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?

Not sure what you mean - “et cetera” is nine keystrokes.

Nonetheless, Tiro would approve. ⁊c.

Re: NPM: 429 Too Many Requests

#107
post #46
post #36

Earlier quoted context omitted.

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?

Keypresses is a pretty poor metric to base communication upon. It annoys me to see "w/" and "w/o" anywhere except Twitter. The meaning isn't clear to many non-native speakers, and it's jarring — we recognise the most common words by the shape of the whole word, so it's easier to read "with" and "without".

"&" is a ligature for the letters "et". A traditional way to handwrite it, other than as &, is a "crossed epsilon", something like Ɛ̸, which looks more like "et". There's a Unicode character closer to this form: 🙲. I have no preference between 🙲, &, etc. and et cetera — none is common enough that I would recognize it by shape while reading prose.

Re: NPM: 429 Too Many Requests

#108
post #98
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)

In GH in particular, I’m not sure why images are allowed to be rendered in comments at all. They are almost always harmful. External links can be used instead

I find them very useful when working with software with images (e.g. maps), and when users supply screenshots with their issue reports.

Re: NPM: 429 Too Many Requests

#109
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.

Idk, it wasn't much more annoying than the 400th person chiming in with a "me too" before that. I already might have completely missed a comment explaining the situation between all these.

Actually those animated gifs might have been better than all those "me too", since a text-only post informing about the situation would have stuck out much better.

Re: NPM: 429 Too Many Requests

#110
post #98
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)

In GH in particular, I’m not sure why images are allowed to be rendered in comments at all. They are almost always harmful. External links can be used instead

Issue screenshots? I work on a video player and almost every issue has a screenshot in it, without which we would be very lost.
Post reply on HN