colorette

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

I started to mention Colorette when author asked me. First mention (it was changed later) was added 6 days ago (threat was created 2 days ago): https://www.npmjs.com/package/nanocolors/v/0.1.2 Webpack team ask Colorette’s author to rollback API 2.x changes here (discussion was cleaned by Colorette’s author, but he said that it is how it see the best API): 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.

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,

Another side of this story https://twitter.com/sitnikcode/status/1441824191624486924 Also at the end Colorette’s author back-ported Nano Colors performance optimizations, but this time he refuse to mention another developer. https://github.com/jorgebucaran/colorette/issues/78

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.

From your own code: 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, FITNE

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.