Hacker GitHub

← All repos

ai/nanocolors

View on GitHub ↗ ★ 856 JavaScript archived

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

16 mentions on Hacker News by 12 people: 0 stories, 16 comments · first 2021-09-26 · latest 2021-09-29

Mentions per year 16 mentions · busiest year 2021 (16)
20082026
  1. …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]:…
  2. …measurements they're discussing are on the order of tens-of-millions of operations per second: https://github.com/ai/nanocolors#benchmarks Are the contents of your terminal changing that frequently?
  3. …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
  4. …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…
  5. …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…
  6. …and keep the origin history? I clearly explain the reasons of fork creation and the changes https://github.com/ai/nanocolors/wiki/Colorette-Changes What “fork rules” did I violate?
  7. …of colorette is on top of Nano Colors docs with clear list of why fork was created and the changes https://github.com/ai/nanocolors#nano-colors
  8. It's literally atributed in the readme file https://github.com/ai/nanocolors
  9. …one license, with one copyright (new author), but they are citing the other work in the copyrights: https://github.com/ai/nanocolors/pull/15/commits/182c767583b...
  10. …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...
  11. …in after the Twitter thread [2]. 1 - https://twitter.com/DerianAndre/status/1441851684095811585 2 - https://github.com/ai/nanocolors/commits/main?after=566a49b0...
  12. He literally took his project and branded as his. https://github.com/ai/nanocolors/commits/main?after=566a49b0... Disgusting.
  13. …The issue only being resolved [1] when public shame was involved should close this case. 1 - https://github.com/ai/nanocolors/blob/main/COPYRIGHT#L1-L3
  14. …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…
  15. See also https://github.com/ai/nanocolors/pull/14
  16. It looks like nanocolors is a fork of colorette with a few (substantial?) changes, see https://github.com/ai/nanocolors/wiki/Colorette-Changes . However, the author of nanocolors, Andrey Sitnik, only added attribution info about colorette…