Live data from Hacker News

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

twitter.com

141–150 of 309 posts

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

#141
post #129
post #127

Earlier 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

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

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

#142
post #48

Earlier quoted context omitted.

It wasn't fixed until he went public. As a popular maintainer ai knows how to fork while preserving history. Not to mention that he originally claimed the API was merely "inspired" by colorette.

I know. Maybe it was bad intent, maybe it was just missed. But it was fixed quickly. Now it is fixed. That’s the important part.

I don't think it could have been "just missed" when the license and his history were stripped from the code.

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

#144

https://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.

I feel like I'm in a bizarro world the number of people supporting the forker or trying to make it off like its just an innocent mistake.

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

#145
post #51

Earlier quoted context omitted.

It does not indicate a bad actor. It is bad actor. Attribution is not a "wish" of the original creator that you should feel morally obliged to follow. It is a legal prerequisite of you being allowed to make a fork of it for free, under the licence given by the author.

It’d be helpful for anyone downvoting this to point out the factual error that I can’t see.

It's downvoted because it's a semantic nitpick based on a misunderstanding; it doesn't have enough meaning to contain a "factual error".

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

#146

Earlier quoted context omitted.

Everything in the npm ecosystem pretty much has to be MIT, or none of it would work. You could poison most of the web dev ecosystem by changing the license on a handful of packages to GPL...

Why? You could use GPL package in MIT licensed library.

Yes and then anyone using said library would have to open source their work.

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

#147
post #73

I keep thinking about this event and it seems like a fractal of bizarre phenomena. The act of stripping git history and attribution while forking is itself malicious, but then aggressively creating pull requests across major projects to use the new version and rack up your download count (???), then picking petty fights with the creator of the original over attribution (????), and the fanbase (?????) of the forker do…

> The act of stripping git history and attribution while forking is itself malicious,

Well, okay, the forking could have been more politely, but author is a bit fast to pull the pirate card. It's a free/libre fork of a free/libre project after all.

> nanocolors implementation and API are the same as Colorette. You essentially pirated my work.[0]

[0]: https://twitter.com/jorgebucaran/status/1441728642711572486

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

#148
post #102
post #94

Earlier quoted context omitted.

The absolutely crazy thing is the person who caused this doesn't even think they did anything wrong: https://github.com/babel/babel/pull/13783#issuecomment-92724... And there are people supporting their position. I think because JS is such a large tent, there are folks not familiar with licenses and general norms in this space. I don't think it's something that being reasonable and pointing things out wouldn't fix. A…

> I think because JS is such a large tent, there are folks not familiar with licenses and general norms in this space. It's worth pointing out that this is all about a bunch of packages that decorate strings with ANSI colour escape sequences... I'm not saying it's worthless, or that there is nothing wrong in principle - but it's a lot of noise over something easily replicable from scratch - something simple enough th…

I don't think this is a fair framing. This isn't left-pad - it's a library that abstracts something people find annoying, and finding the right abstraction can be difficult even if the final code doesn't seem complicated. Add in a few years of bug fixes and whatnot, and it seems pretty rude to dismiss the result as "easily replicable from scratch".

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

#149
post #127
post #102

Earlier quoted context omitted.

> I think because JS is such a large tent, there are folks not familiar with licenses and general norms in this space. It's worth pointing out that this is all about a bunch of packages that decorate strings with ANSI colour escape sequences... I'm not saying it's worthless, or that there is nothing wrong in principle - but it's a lot of noise over something easily replicable from scratch - something simple enough th…

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.

https://github.com/jonschlinkert/info-symbol https://github.com/jonschlinkert/success-symbol https://github.com/jonschlinkert/warning-symbol https://github.com/jonschlinkert/error-symbol

My personal favourite is making every single ansi colour into a separate package, and then making `ansi-colors` which depends on all of them, and all of these packages are just a single function call with a provided number. It's honestly insane.

https://github.com/jonschlinkert/ansi-black

https://github.com/jonschlinkert/ansi-reset

https://github.com/jonschlinkert/ansi-bold

https://github.com/jonschlinkert/ansi-dim

https://github.com/jonschlinkert/ansi-italic

https://github.com/jonschlinkert/ansi-underline

https://github.com/jonschlinkert/ansi-inverse

https://github.com/jonschlinkert/ansi-hidden

https://github.com/jonschlinkert/ansi-strikethrough

https://github.com/jonschlinkert/ansi-black

https://github.com/jonschlinkert/ansi-red

https://github.com/jonschlinkert/ansi-green

https://github.com/jonschlinkert/ansi-yellow

https://github.com/jonschlinkert/ansi-blue

https://github.com/jonschlinkert/ansi-magenta

https://github.com/jonschlinkert/ansi-cyan

https://github.com/jonschlinkert/ansi-white

https://github.com/jonschlinkert/ansi-gray

https://github.com/jonschlinkert/ansi-grey

https://github.com/jonschlinkert/ansi-bgblack

https://github.com/jonschlinkert/ansi-bgred

https://github.com/jonschlinkert/ansi-bggreen

https://github.com/jonschlinkert/ansi-bgyellow

https://github.com/jonschlinkert/ansi-bgblue

https://github.com/jonschlinkert/ansi-bgmagenta

https://github.com/jonschlinkert/ansi-bgcyan

https://github.com/jonschlinkert/ansi-bgwhite

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

#150

This is going to sound like a dumb question and is certainly going to be an unrelated tangent, but: why in the world does the Node ecosystem have half a dozen competing terminal colorization libraries? Is that much CLI tooling really being written in JavaScript? I spend virtually my entire workday in a terminal, and I’ve never once needed a CLI tool written in JS. Where is all this code going ?

Overwhelming majority of modern web frontend development is done with build tools written in JS. Node is a popular choice for backend and that also generates a lot of lines of terminal output.
Post reply on HN