131–140 of 171 posts
Earlier quoted context omitted.
It's just a mirror service address, the NPM package is the same. Worrying too much about cybersecurity is a bit of a storm in a teacup.
Well, how do you know it's "just" a mirror service, and it is not using a zero-day to exploit your system, by installing a root-kit or copying your code to their servers? I agree that it's a valid concern.
Includes a built-in package manager for resource fetching, thus no need for NPM.
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)
there's also quite some personal contributors in github, for these it's not a work context to begin with
I'm seeing comments on here that some of these people are acting like high school kids. Some of them probably are high school kids.
And that's fine. One of the biggest goals of Open Source in the first place is that software shouldn't only be developed and used by professionals. If you want that reality, you have to tolerate that unprofessional people are sometimes going to be part of the surrounding conversation for some projects.
In short, if the NPM maintainers hate this, they can modify community rules or remove spammy posts. And if they don't hate it, then I don't really get what the big deal is about allowing people to be unprofessional when talking about code -- other than maybe arguing that Github should have better filtering tools for readers.
Earlier quoted context omitted.
I think this is partly a result of two things. 1. GitHub presents an interface that encourages Reddit style behaviour. 2. NPM outages are essentially a meme in themselves at this point. Both of them together create a perfect storm.
I have no comment on #2, as I don't play in that sandbox. However, regarding #1... the interface allows people to post images in their comments on issues. This has a valid, useful reason - for showing screenshots of bugs, for example. The problem is not the interface. The problem is the people using the interface.
1. When I sign up for updates I get spammed with notifications -- you should be able to listen only to updates from the project maintainers.
2. I can't find the official status -- again, this is a problem because the official status is buried inside a conversation thread. This could be pretty easily solved by allowing maintainers to pin comments, or by (again) allowing filtering comments by project maintainers.
3. Replies to comments get lost in the memes -- because Github issues don't support threading, and (again) there's no filter by replies or mentions.
Or...
4. Memes just make me mad because they're unprofessional -- and okay, this one is the community. But I just can't muster the energy to care about this, or to feel sympathy for the people who care about it. If we were talking about abuse, or 3rd-party unwanted advertisements, maybe I could get on board. But a gif is not a real problem.
The fact that Github has literally no searching at all on issue threads is the fault of the tool, not the community. The fact that NPM doesn't have an official status page is the fault of NPM, not the community.
Earlier quoted context omitted.
> [..] 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 n…
In addition to the first reply to your post, you may find it strange but having dress codes actually help promote diversity in workplaces.
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.
when you look at rust repo, everyone feels like they are going to die, just like the C repos, full of boring 60yo people
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)
Like everything else, Eternal September also got reimplemented in JavaScript.
Eternal September or the September that never ended is Usenet slang for a period beginning in September 1993, the month that Internet service provider America Online began offering Usenet access to its many users, overwhelming the existing culture for online forums. -- Wikipedia
Earlier quoted context omitted.
I have no comment on #2, as I don't play in that sandbox. However, regarding #1... the interface allows people to post images in their comments on issues. This has a valid, useful reason - for showing screenshots of bugs, for example. The problem is not the interface. The problem is the people using the interface.
Eh... I think 90% of the complaints people have here are related to the interface. 1. When I sign up for updates I get spammed with notifications -- you should be able to listen only to updates from the project maintainers. 2. I can't find the official status -- again, this is a problem because the official status is buried inside a conversation thread. This could be pretty easily solved by allowing maintainers to pi…
Earlier quoted context omitted.
Like everything else, Eternal September also got reimplemented in JavaScript.
History: Eternal September or the September that never ended is Usenet slang for a period beginning in September 1993, the month that Internet service provider America Online began offering Usenet access to its many users, overwhelming the existing culture for online forums. -- Wikipedia