A notable JavaScript developer shamelessly copied one of my most downloaded nod

Post by swiley » Sun, Sep 26, 2021, 9:01 PM UTC

woodruffw wrote: post #41

ctvo wrote: post #38

I'm losing my mind with people who keep replying with "That's open source baby! Don't make it open source if you don't like!" The problem with this behavior is as follows: - The MIT license requires attribution of the original work. The author contacted the person who forked this privately [1]. It wasn't done until the Twitter thread. - Questionably the fork was renamed and didn't include git history to make the firs…

I was on the forker’s side of things until those last two points: I don’t think anybody should have to justify creating a fork, but the (seemingly intentional) stripping of the revision history and absence of attribution indicates a bad actor to me.

Post by nrabulinski » Sun, Sep 26, 2021, 9:08 PM UTC

iskin wrote: post #252

nrabulinski wrote: post #245

Earlier quoted context omitted.

Please tell me why didn’t you just click the fork button or mentioned Colorette from the very beginning but instead started out maliciously and tried to use your influence to your advantage? To me there’s no other explanation than you tried to sweep it under the rug but it didn’t work out so you’re playing the victim card.

As I mention here, because Nano Colors it's not just fork of Colorette. It was created as a mix of Colorette and kleur. https://twitter.com/sitnikcode/status/1441827379454746637?s=... Fork button will not work for this case.

Post by nextaccountic » Sun, Sep 26, 2021, 9:11 PM UTC

smsm42 wrote: post #186

kgeist wrote: post #175

Earlier quoted context omitted.

His explanation on Reddit: "The way I learned how to program was by publishing one project a day that used a specific language feature I was trying to learn. No one even looked at my projects or used them until I had quite a few published. I didn't even want people to use them at that point, since I had no idea what I was doing. Then one day I realized that people were actually using some of the things I published as…

Maybe public common repository shouldn't be used as a dumping ground for every random guy learning how to make their first script. It's a bit like learning to drive by going to a public highway and just starting driving at random directions and then saying "why are you folks screaming? I'm just learning, it's depressing you always assume the worst!"

Post by iskin » Sun, Sep 26, 2021, 9:22 PM UTC

enumjorge wrote: post #118

riffraff wrote: post #92

Earlier quoted context omitted.

Cascade of attention deficit[0]? JS is a vast ecosystem with little barriers to entry, and > Fixing bugs isn't fun; going through the bug list isn't fun; but rewriting everything from scratch is fun (because "this time it will be done right", ha ha) and so that's what happens, over and over again. I don't think there's anything malicious going on, except a lot of people doing JS. [0] https://www.jwz.org/doc/cadt.html

> I don't think there's anything malicious going on The dev who copied the code forked someone’s repo, went out of his way to remove attribution and git history, sent PRs to replace the original package in other libraries with his own version, and when called out on it got defensive instead of apologizing. I think malicious is a fair way to describe his behavior.

Post by hamburglar » Sun, Sep 26, 2021, 9:42 PM UTC

kgeist wrote: post #175

zkldi wrote: post #149

Earlier quoted context omitted.

For what it's worth, this is also all the work of one person who spammed NPM with micropackages to boost his download counts. This meme attacking `npm` for nonsense like `is-odd` is quite literally the result of one person resume boosting. For every one thing, he broke it down into as many possible packages as possible, and all of his packages depend on 20 more of his packages. It's like a fractal of resume boosting.…

His explanation on Reddit: "The way I learned how to program was by publishing one project a day that used a specific language feature I was trying to learn. No one even looked at my projects or used them until I had quite a few published. I didn't even want people to use them at that point, since I had no idea what I was doing. Then one day I realized that people were actually using some of the things I published as…