It's literally atributed in the readme file https://github.com/ai/nanocolors
A notable JavaScript developer shamelessly copied one of my most downloaded nod
171–180 of 309 posts
Re: A notable JavaScript developer shamelessly copied one of my most downloaded nod
#172> We just have to all remember how you copied colorette from kleur. Seem everyone in the ansi space all copying from each other. Just congratulate nanocolors — spotting a perf boost where no one else did. Took the best of all worlds.
When you make something open-source, you give others free right to copy your work and release their own derivative version. That’s basically the point of open-source. And this version might become more popular and yours.
BUT, if you copy someone else’s work you NEED to give them attribution. Which is what nanocolors did wrong.
GitHub should add a feature which lets you attribute various parts of your code to other open-source projects (or better, auto-attributes them for you). And then when a project gains reputation it’s attributed projects gain some also. This is already done with forks / packages, but it could be more explicit and for vendor dependencies and regions of code as well.
Re: A notable JavaScript developer shamelessly copied one of my most downloaded nod
#173Earlier quoted context omitted.
I thought it was a joke your is-odd comment. But no it is at version 3.0.1 and has 2.1 million downloads a month[0]... And it has a dependency to is-number. With the performance of today's tree shaking systems I wonder why there is not a simple math lib. [0] https://www.npmjs.com/package/is-odd
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.…
Re: A notable JavaScript developer shamelessly copied one of my most downloaded nod
#174Earlier quoted context omitted.
It's pretty crazy. For whatever reason there is a substantial culture around NPM usage of preferring to depend on lots of trivial packages, over writing simple inline equivalents. And it's recursive, which can mean depending on what seems to be a modest but useful package at the top of that hierarchy ends up pulling down 10k packages. I think this makes it easier to acquire an inflated sense of importance when an aut…
In fairness to the OP he did optimize the hell out of his colorette lib, it's about 1/10th the size of the widely adopted chalk lib and performs way better. Back in the day I remember he was (rightly) complaining that the chalk author submitted PRs to get chalk used in as many libs as possible, while colorette (or whatever it was called--it has a different name before) was the technically superior solution to the pro…
Re: A notable JavaScript developer shamelessly copied one of my most downloaded nod
#175Earlier quoted context omitted.
I thought it was a joke your is-odd comment. But no it is at version 3.0.1 and has 2.1 million downloads a month[0]... And it has a dependency to is-number. With the performance of today's tree shaking systems I wonder why there is not a simple math lib. [0] https://www.npmjs.com/package/is-odd
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.…
"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 a learning exercise, and I started going back and fixing and improving that code. Rinse and repeat. That's pretty much all I did.
Why is the default for people to assume the worst all the time? It's depressing as hell."
If true, it's kind of sad so many people badmouth him.
Re: A notable JavaScript developer shamelessly copied one of my most downloaded nod
#176Re: A notable JavaScript developer shamelessly copied one of my most downloaded nod
#177Aside from who’s right and who’s wrong, although I do agree with this is an unattributed fork, the idea that JS OSS devs are incentivized to do this to increase their downloads number is absurd. Maybe we need to replace that with a star system including both security vulnerabilities and downloads that is less dopamine-inducing than a moving number.
Re: A notable JavaScript developer shamelessly copied one of my most downloaded nod
#178Earlier quoted context omitted.
Combination of so much JS programmers being * Young * Hipster * From bootcamps without any other serious knowledge. * A culture of resume padding * A total lack of care about security, performance or reliability.
Riddled with insecurity yet somehow lacking humility.
Re: A notable JavaScript developer shamelessly copied one of my most downloaded nod
#179Earlier 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…
Re: A notable JavaScript developer shamelessly copied one of my most downloaded nod
#180https://twitter.com/equinusocio/status/1441732243727192087?s... > You should think this "wow, the author of one of the most popular frontend tools of today just used my work as reference. It's an honor." By far my favorite and most ridiculous tweet I've seen in this thread.