3 ms·

Aside 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

by exdsq 5y ago

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

Zababa 5y ago
Bugs should also come into play. Some people mentioned that the developer of nanocolors removed some edge case handling to make his microbenchmarks faster. I like fast software as much as anyone, but more than that I love correct software. I'd rather wait for something to finish than have to search why something exploded. Especially if it's a dependency of a dependency that I use, which is the case with Babel.
iskin 5y ago
Why it is a unattributed fork if Colorette is mentioned in docs, COPYRIGHT and origin commits are in history?
- bsagdiyev 5y ago
  You should mention your conflict of interest as the nanocolors “developer”.
  - iskin 5y ago
    I am mentioning it in Babel PRs: > It will have a good support. My other projects from nano-series like very popular Nano ID shows a minimal number of bugs and excellent response time.
    - exdsq 5y ago
      He meant you should mention your bias in the comments on HN, naturally you’re going to think you’re right (and they will think they’re right). It was my understanding that the commit history wasn’t originally saved - maybe this was wrong, did you have the commit history immediately after copying the code base? The main issue is then replacing it in open source software where the other version exists without due cause. Should we copy your code, attribute it to you in a readme, and slightly optimize some of your code to replace your efforts everywhere?
      - iskin 5y ago
        I copied one file and I didn't know a way to keep the history of this file. When people later explained how to keep the history of single file I tried to restored it.

by exdsq 5y ago

Zababa 5y ago

Bugs should also come into play. Some people mentioned that the developer of nanocolors removed some edge case handling to make his microbenchmarks faster. I like fast software as much as anyone, but more than that I love correct software. I'd rather wait for something to finish than have to search why something exploded. Especially if it's a dependency of a dependency that I use, which is the case with Babel.

iskin 5y ago

Why it is a unattributed fork if Colorette is mentioned in docs, COPYRIGHT and origin commits are in history?

bsagdiyev 5y ago
You should mention your conflict of interest as the nanocolors “developer”.
- iskin 5y ago
  I am mentioning it in Babel PRs: > It will have a good support. My other projects from nano-series like very popular Nano ID shows a minimal number of bugs and excellent response time.
  - exdsq 5y ago
    He meant you should mention your bias in the comments on HN, naturally you’re going to think you’re right (and they will think they’re right). It was my understanding that the commit history wasn’t originally saved - maybe this was wrong, did you have the commit history immediately after copying the code base? The main issue is then replacing it in open source software where the other version exists without due cause. Should we copy your code, attribute it to you in a readme, and slightly optimize some of your code to replace your efforts everywhere?
    - iskin 5y ago
      I copied one file and I didn't know a way to keep the history of this file. When people later explained how to keep the history of single file I tried to restored it.