4 ms·
> I mean, people were putting spam packages in NPM just to get SEO on some outside webpage through the default NPM package webpages. People were squatting and s
by zozbot234 7y ago
> I mean, people were putting spam packages in NPM just to get SEO on some outside webpage through the default NPM package webpages. People were squatting and stealing package names. Leftpad... the community management here is nightmarishly hard
It's not NPM's fault (well, other than wrt. the leftpad thing), it's all about the "community". The Javascript open source community is a dumpster fire.
- VonGuard 7y agoCorrect, it is not their fault. But they ended up spending all their time on it, and in an unproductive manner, I feel.
- gedy 7y agoOh please... I’ve solved more customer needs and business value from this "dumpster fire" than I have with other "real languages" I've worked with in my career. Give it some credit.
- sarakayakomzin 7y agoI've worked with a lot of developers who have provided business value by importing leftpad rather than writing code.
- 411111111111111 7y agoWhat does your productivity in js have to do with js having a terrible community?
- emilsedgh 7y agoIt's the [terrible] community that provides so much value in form of npm, not that js is really that much more productive.
- thaumasiotes 7y agoThere's no contradiction between providing a ton of value and being horrible. You know how people ask "why do people stay in abusive marriages?"? That's why. On a bigger scale, this passage from The Early Chinese Empires: Qin and Han stuck with me: > Today, in a stretch of about 1,100 miles, the Yellow River moves along 11 yards above the plain. But dikes do not control silting, and floods continued to occur on an ever larger scale. On more than 1,500 occasions during the history of imperial China the Yellow River burst its dikes, destroying farmland, killing villagers, and earning its description as "China's sorrow".
- nimonian 7y agoI don't think it's fair to victims of abusive relationships for you to use this analogy: the truth is far darker and more complex, and survivors deserve more credit than you're giving them. I could give you my story as an example in case you haven't ever been exposed to this kind of abuse, but maybe it is enough for me to say we should all think twice before using such an extreme and unique scenario in our arguments.
- nindalf 7y agoTheir productivity is directly related the to vast ecosystem of packages available. Those packages were written and maintained by the community. They are rebutting the assertion that this community is bad. It can't be that bad if they're helping millions of developers solve real problems around the world.
- 411111111111111 7y agoPeople can be ptsd inducingly toxic and still deliver quality code. These things aren't related
- deleted 7y ago[deleted]
- dspillett 7y agoIt's like modern fighter jets which are designed to be unstable so they are more manoeuvrable, aided by the computer controls to stop that instability being dangerous. If the computer systems fail, the pilot will not cope and the jet will crash and burn. The JS community is unstable, but in a way that produces useful things rapidly. Stuff just gets thrown out there and the good parts stick. Certain dampening factors protect you from the most dangerous effects of this (unless you live your life at the bleeding edge) like the jet's computer controlled micro-interventions protecting the pilot form how jittery the airframe actually is. Occasionally this goes wrong and the protection fails. "Leftpad" was one such matter that caused thing to crash and burn temporarily. Luckily unlike an expensive jet hitting the ground, the damage from such incidents is relatively easy to repair after the fact. The throw-it-out-and-see-if-it-works part isn't the only issue with the JS community but it is a significant one and does relate to some of the others, though one that does provide some benefit in the form of forward momentum.
- deleted 7y ago[deleted]
- 1337shadow 7y agoDo they have an ORM that generates migrations from model definitions nowadays ?
- z3t4 7y agoThe JS community is the worlds biggest open source community and that's what they've been buying.
- ex3ndr 7y agoNo, it is an NPM fault. Their team is highly toxic and selfish.
- andrewaylett 7y agoAs an online community gets larger, the probability of a member deserving a comparison involving Nazis or Hitler approaches 1? That the JS community is huge and overwhelmingly newer to the industry than (for example) me does not excuse bad behaviour. What it _does_ excuse is a lack of awareness of history and historical context. And the solution to that is education. It pains me to see so many wheel-reinventions, both technical and social. But the flip side is that people who don't know something's not supposed to be possible will _sometimes_ manage to do it anyway. NPM, on the other hand, seemed very much to be all about package management being a simple problem, and learned the hard way that there's a reason why other systems have more complexity.