181–190 of 309 posts
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
This is going to sound like a dumb question and is certainly going to be an unrelated tangent, but: why in the world does the Node ecosystem have half a dozen competing terminal colorization libraries? Is that much CLI tooling really being written in JavaScript? I spend virtually my entire workday in a terminal, and I’ve never once needed a CLI tool written in JS. Where is all this code going ?
Good comment by one of the Chalk maintainers https://github.com/babel/babel/pull/13783#issuecomment-92731...
Earlier quoted context omitted.
For what it's worth, this is also all the work of one person who spammed NPM with micropackages to boost his download counts. This meme attacking `npm` for nonsense like `is-odd` is quite literally the result of one person resume boosting. For every one thing, he broke it down into as many possible packages as possible, and all of his packages depend on 20 more of his packages. It's like a fractal of resume boosting.…
His explanation on Reddit: "The way I learned how to program was by publishing one project a day that used a specific language feature I was trying to learn. No one even looked at my projects or used them until I had quite a few published. I didn't even want people to use them at that point, since I had no idea what I was doing. Then one day I realized that people were actually using some of the things I published as…
> The color reset, in ansi. [1]
> The color strikethrough, in ansi. [2]
etc.
Which don't really make any sense.
[1] https://github.com/jonschlinkert/ansi-reset [2] https://github.com/jonschlinkert/ansi-strikethrough
What am I missing?
Earlier quoted context omitted.
For what it's worth, this is also all the work of one person who spammed NPM with micropackages to boost his download counts. This meme attacking `npm` for nonsense like `is-odd` is quite literally the result of one person resume boosting. For every one thing, he broke it down into as many possible packages as possible, and all of his packages depend on 20 more of his packages. It's like a fractal of resume boosting.…
His explanation on Reddit: "The way I learned how to program was by publishing one project a day that used a specific language feature I was trying to learn. No one even looked at my projects or used them until I had quite a few published. I didn't even want people to use them at that point, since I had no idea what I was doing. Then one day I realized that people were actually using some of the things I published as…
Good comment by one of the Chalk maintainers https://github.com/babel/babel/pull/13783#issuecomment-92731...
Chalk maintainers basically discard the performance improvement as micro-benchmarking (i.e. "doesn't matter in the real world"). Chalk maintainers also say tree shaking doesn't matter in the real world.
Why do they minimize these 2 improvements? If 2 libraries are equivalent, I'd go with the ones with extra improvements.
Chalk maintainers also mentioned that chalk would have no dependencies soon (not now, but soon). They also mentioned that chalk is well maintained for over 10y.
So, over the past decade, they can't remove dependencies? Suddenly, nanocolors show up, and now they will remove dependencies soon? That doesn't sound well-maintained.
Speed/tree-shaking aside, having no dependencies is a huge improvement.
Earlier quoted context omitted.
> Versions of software can have different licenses, and the license for each version is the license that the repo was under when that version was committed. Not particularly wrong, just adding: There can even be additional licensing terms that aren't documented in the git history so they wouldn't be visible there. And there is another sticky detail: So if the original copy would have violated any of the licensing ter…
Yes, I think your comment adds a lot to mine. Licensing of version control history might need to have a legal debate, actually.
You can't do this with lax permissive licenses nor with copyleft as they allow to modify the work, which would mean the right to modify the history.
He literally took his project and branded as his. https://github.com/ai/nanocolors/commits/main?after=566a49b0... Disgusting.