▲ | jmull 4 days ago | |||||||||||||||||||||||||||||||
Yeah, I get that learning the codes is a little annoying, but not actually harder than finding, incorporating, and learning one of the APIs here. Also one is standard while the other is not. Seems a bit nuts to use a package for this. | ||||||||||||||||||||||||||||||||
▲ | junon 4 days ago | parent | next [-] | |||||||||||||||||||||||||||||||
Hi, missing a lot of history here. When Chalk was written, colors in the terminal wasn't a flashy thing people tried to do very often, at least not in the JS world. Coming from browsers and wanting to make CLI apps using the flashy new Node.js 0.10/0.12 at the time saw a lot of designers and other aesthetically-oriented folks with it. Chalk filled a hole for people to do that without needing to understand how TTYs worked. Node.js proper has floated the idea of including chalk into the standard libraries, FWIW. | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||
▲ | int_19h 3 days ago | parent | prev [-] | |||||||||||||||||||||||||||||||
I would argue that ANSI color output should be something natively supported in stdlib for any general purpose or systems programming language today. Precisely for this reason - it has been a standard for a very long time, and for several years now (since Windows enabled it by default) it is a truly universal standard de facto as well. This is exactly the kind of stuff that stdlib should cover. |