colorette VS nanocolors

Here are the smallest libs: picocolors (2.6KB), kleur (2.7KB), ansis (3.2KB) and colorette (3.3KB), the rest are at least double larger.

https://npm.im/colorette (16.9M weekly downloads) https://github.com/jorgebucaran/colorette (1.4k stars)

https://github.com/jorgebucaran/colorette/blob/main/LICENSE....

Copyright © Jorge Bucaran <https://jorgebucaran.com>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

https://github.com/jorgebucaran/colorette/issues/70

> why not drop your fork now that colorette has changed the API back?

Author continued to act impulsively. He rolled back API in patch release instead of major made breaking changes.

Am I missing something here? Are https://github.com/jorgebucaran/colorette/blob/main/index.js and https://github.com/ai/nanocolors/blob/main/index.js the essentially what people are fighting over? It looks like a bunch of constants and about the same amount of code you'd find in a Stack Overflow answer.

There's something weird about an ecosystem that turns this code into something worth fighting over.

Am I right that this is the important part of the library?

https://github.com/jorgebucaran/colorette/blob/d1ff3a7/index...

I agree that the author clearly spent a lot of time polishing it, hence the pride and feeling of betrayal.

What is even going on here? https://github.com/jorgebucaran/colorette/issues/78. They're arguing about who should have attribution for adding a single "!s &&" to improve performance? What happened with the world where open-source was about creating cool projects together, not about who has the most stars on GitHub?

To be honest, this is the general feeling I get from the JavaScript community: Instead of working together to improve existing projects it's all about launching new alternative packages and get everyone to switch to your new fancy project. This causes a never ending churn where we jump between (incompatible) libraries with very little actual improvements.

You have a new benchmark results after you backported Nano Colors optimizations and refused to mentioned it

https://github.com/jorgebucaran/colorette/issues/78

Just look at performance changes history,

You can see the original commit history in old forks of nanocolor, e.g:

* https://github.com/antonk52/nanocolors/commits/main * https://github.com/corysimmons/nanocolors/commits/main?after...

You can, indeed, see that they lack all of the original repo's commits.