HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ai
nanocolors
JavaScript2021–2021
ai / nanocolors · Archived

nanocolors

Use picocolors instead. It is 3 times smaller and 50% faster.

12Distinct people
16Mentions
0Explicit recommenders
856GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Use picocolors instead. It is 3 times smaller and 50% faster.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval16 dated mentions

Observed mentions: 2021-09-26 11:24:16 UTC to 2021-09-29 07:37:15 UTC.

012342021-09-26 09:00:00 UTC to 2021-09-26 12:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsSep 26, 09:002021-09-26 12:00:00 UTC to 2021-09-26 15:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2021-09-26 15:00:00 UTC to 2021-09-26 18:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-09-26 18:00:00 UTC to 2021-09-26 21:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-09-26 21:00:00 UTC to 2021-09-27 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-09-27 00:00:00 UTC to 2021-09-27 03:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-09-27 03:00:00 UTC to 2021-09-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-27 06:00:00 UTC to 2021-09-27 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-27 09:00:00 UTC to 2021-09-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-27 12:00:00 UTC to 2021-09-27 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-27 15:00:00 UTC to 2021-09-27 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-27 18:00:00 UTC to 2021-09-27 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 27, 18:002021-09-27 21:00:00 UTC to 2021-09-28 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-09-28 00:00:00 UTC to 2021-09-28 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-28 03:00:00 UTC to 2021-09-28 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-28 06:00:00 UTC to 2021-09-28 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-28 09:00:00 UTC to 2021-09-28 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-28 12:00:00 UTC to 2021-09-28 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-28 15:00:00 UTC to 2021-09-28 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-28 18:00:00 UTC to 2021-09-28 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-28 21:00:00 UTC to 2021-09-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-29 00:00:00 UTC to 2021-09-29 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-29 03:00:00 UTC to 2021-09-29 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-29 06:00:00 UTC to 2021-09-29 09:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 29, 06:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 26, 09:002021-09-26 09:00:00 UTC2021-09-26 12:00:00 UTC303
Sep 26, 12:002021-09-26 12:00:00 UTC2021-09-26 15:00:00 UTC404
Sep 26, 15:002021-09-26 15:00:00 UTC2021-09-26 18:00:00 UTC303
Sep 26, 18:002021-09-26 18:00:00 UTC2021-09-26 21:00:00 UTC202
Sep 26, 21:002021-09-26 21:00:00 UTC2021-09-27 00:00:00 UTC101
Sep 27, 00:002021-09-27 00:00:00 UTC2021-09-27 03:00:00 UTC101
Sep 27, 03:002021-09-27 03:00:00 UTC2021-09-27 06:00:00 UTC000
Sep 27, 06:002021-09-27 06:00:00 UTC2021-09-27 09:00:00 UTC000
Sep 27, 09:002021-09-27 09:00:00 UTC2021-09-27 12:00:00 UTC000
Sep 27, 12:002021-09-27 12:00:00 UTC2021-09-27 15:00:00 UTC000
Sep 27, 15:002021-09-27 15:00:00 UTC2021-09-27 18:00:00 UTC000
Sep 27, 18:002021-09-27 18:00:00 UTC2021-09-27 21:00:00 UTC000
Sep 27, 21:002021-09-27 21:00:00 UTC2021-09-28 00:00:00 UTC101
Sep 28, 00:002021-09-28 00:00:00 UTC2021-09-28 03:00:00 UTC000
Sep 28, 03:002021-09-28 03:00:00 UTC2021-09-28 06:00:00 UTC000
Sep 28, 06:002021-09-28 06:00:00 UTC2021-09-28 09:00:00 UTC000
Sep 28, 09:002021-09-28 09:00:00 UTC2021-09-28 12:00:00 UTC000
Sep 28, 12:002021-09-28 12:00:00 UTC2021-09-28 15:00:00 UTC000
Sep 28, 15:002021-09-28 15:00:00 UTC2021-09-28 18:00:00 UTC000
Sep 28, 18:002021-09-28 18:00:00 UTC2021-09-28 21:00:00 UTC000
Sep 28, 21:002021-09-28 21:00:00 UTC2021-09-29 00:00:00 UTC000
Sep 29, 00:002021-09-29 00:00:00 UTC2021-09-29 03:00:00 UTC000
Sep 29, 03:002021-09-29 03:00:00 UTC2021-09-29 06:00:00 UTC000
Sep 29, 06:002021-09-29 06:00:00 UTC2021-09-29 09:00:00 UTC101

What Hacker News says

16 sources
I reached out to him when I could've filed a takedown notice instead. Later, after the tweets, I even asked him to shake hands on the whole thing[1][2][3], but he was already sunk-cost-mode on and determined to die on a stupid hill. Only because I called him out is that we were able to had my git history restored and copyright attributed. > Their attitude since then has left a lot to be desired. That refers to the forker's attitude following the tweets[4][5]. [1]: https://github.com/ai/nanocolors/pull/14#issuecomment-927757... [2]: https://user-images.githubusercontent.com/56996/135221889-52... [3]: https://twitter.com/jorgebucaran/status/1442055448899641348 [4]: https://news.ycombinator.com/item?id=28661094 [5]: https://github.com/jorgebucaran/colorette/issues/78
In A notable JavaScript developer shamelessly copied one of my most downloaded nod
> The absolutely crazy thing is the person who caused this doesn't think they did anything wrong. And now he's saying this of the person he took the work from [1]: 1. "I believe he is a good person, but love colorette too much and prefer impulsive actions ... Impulsive behavior can be very dangerous." 2. "Comments like this [https://news.ycombinator.com/item?id=28662796] shows that his behavior in that case was very questionable. Seems like he is systematically put himself in conflicts." True or not, I find his claims of the victim having impulsive or questionable behavior, and systematically creating conflicts, ironic. On a more positive note - it looks like both parties are starting to discuss a resolution [1]; maybe even co-maintainership of the original work in question [2]. I personally think that would take a lot of guts, from both
Read the rest
parties, given everything that's transpired. I also think johnnyshields in the linked GitHub thread [1] deserves acknowledgement for some noticeably simple, but effective, attempts at facilitating resolution. [1] https://github.com/ai/nanocolors/pull/14#issuecomment-927346... [2] https://twitter.com/jorgebucaran/status/1442055448899641348
In A notable JavaScript developer shamelessly copied one of my most downloaded nod
Which is nowhere near no_wizard's point. And nowhere near what you've done. Gorge Bucaran, author of Colorette, summarizes your actions here https://github.com/ai/nanocolors/pull/14#issuecomment-927134...: "Colorette isn't some obscure project either. It is well used. Now imagine I find a project that meets that description. Clone it. Erase the .git directory. Initialize a new repository. Make a few extraneous changes. Incorrectly benchmark it. Falsely claim improved performance. Tweak the docs. Change the name. Add a logo. Start aggressively promoting it and sending PRs to high-profile projects while leveraging a non-trivial social media following. I'm not against forking a project and adding new value to it. I encourage that. But that's not what's going on here. This is the collector getting away with a new piece for their collection."
Read the rest
Comparing that, to "promoting alternatives" to one of your projects on Twitter, shows a creepy lack of acknowledgement. But that's why we're here, isn't it?
In A notable JavaScript developer shamelessly copied one of my most downloaded nod
I completely agree with it. This is why I used Colorette for a year, promote it and send PRs there. https://twitter.com/sitnikcode/status/1441824191624486924 For for created because Colorette changed API and author didn’t want to change it back. The reasons of fork is clearly desrcibed in project’s docs https://github.com/ai/nanocolors/wiki/Colorette-Changes I mentioned Colorette in Nano Colors docs, COPYRIGHT and keep the origin history. But when Colorette author backported my performance optimizations he refuses to do the same in return.
In A notable JavaScript developer shamelessly copied one of my most downloaded nod
He does seem very aggressive in his attempts to get this into as many popular packages (and/or onto as many machines) as he can in the shortest amount of time. According to the original project's author, he even silently removed loads of edge case handlers until he was called out on it [0]. That seems to have been a really quick and dirty tactic to get his performance numbers up. My spidey senses are tingling too. [0] https://github.com/ai/nanocolors/pull/14#issuecomment-927152...
In A notable JavaScript developer shamelessly copied one of my most downloaded nod
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 first point even worse. Git history was only rebased in after the Twitter thread [2]. 1 - https://twitter.com/DerianAndre/status/1441851684095811585 2 - https://github.com/ai/nanocolors/commits/main?after=566a49b0...
In A notable JavaScript developer shamelessly copied one of my most downloaded nod
It's literally three lines of actual content. It would not take you long to read it. The MIT License (MIT) Copyright © 2021 <copyright holders> 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
Read the rest
, 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. He was violating the license until 19 hours ago: https://github.com/ai/nanocolors/commit/1d86f02ca751ad8c113c... The MIT license is a bad license but in this case the terms of it were clearly being violated by a hostile actor.
In A notable JavaScript developer shamelessly copied one of my most downloaded nod

Showing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.