This was glorious, and it is now implemented in SwiftTerm by default.

While it is true that certain users in a dorm at Darmouth or MIT might carry with them the script to tune their color palette, I believe that users in the wild deserve to keep their retinas.

https://gist.github.com/jake-stewart/0a8ea46159a7da2c808e5be2177e1783

Terminals should generate the 256-color palette

Terminals should generate the 256-color palette. GitHub Gist: instantly share code, notes, and snippets.

Gist
@Migueldeicaza Keep an eye on this PR in Ghostty where the original author and others are investigating OKLAB. https://github.com/ghostty-org/ghostty/pull/10818

@mitchellh Will keep an eye on it, thank you!

I have been researching on and off how you got Ghostty to be this fast, I am still 3x slower. One day, one day.

@Migueldeicaza Dude we should hack on it together one day. I'd love to share any insight. I don't care what terminal people use, I just want all of them to be better. Big fan of what you've done and huge respect to you, it'd be an honor

@mitchellh You are going to make me blush! The respect is mutual, and would love to do it.

My main takeaway is that I really need one thread for IO/parsing independent of the display.

One really interesting bit Ghostty does is to trigger trigger the refresh as soon as the parsing starts - and when the parsing ends, the UI thread unblocks.

Brilliant - I need to do some shuffling before it will work for me. Almost there!

@mitchellh Also, Ghostty's idea of shipping the terminal database and point TERMINFO to it - pure genius.

Never thought of it.

@Migueldeicaza I've never seen terminal maintainers universally agree on something as fast as this proposal
@Migueldeicaza @joe Turns out those are the consequences of an MIT license.
@Migueldeicaza back in our day, the script we used to tune our color palette was called β€œthe brightness and contrast knobs”