You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.
👋 After a couple years of working on this library in the background (late 2021), several notable events have happened that don’t make this worth maintaining for me:
Mixing colors through Oklab via color-mix() is now supported in CSS in all major browsers, and is safe to use in web projects today.
Culori also got Oklab support
Culori added Oklab/Oklch support, and if you use the “tree-shakeable” version of colori/fn, you can basically get the footprint of better-color-tools at only a few kB gzip, but with a more stable library and support for more options.
Oh, and did I mention culori/fn is a whopping 5-10× faster than this library for the same package size? 🚀🚀🚀
Frankly, I don’t have the resources to try and tune better-color-tools to be that fast.
All of the above are developments I have welcomed, and couldn’t be happier for 🙂. But it’s made maintaining this library not worth the effort.
Though I considered the possibility of this library simply wrapping culori/fn, I’m not going to do that. Because creating unnecessary abstractions don’t make a good npm package.
Thanks to all those who tried this library and liked the API. But migrating to culori/fn for all your color needs will not only yield a better experience; you’ll also be contributing to better color science tools. And in the end, that’s what matters. 🎨
The text was updated successfully, but these errors were encountered:
👋 After a couple years of working on this library in the background (late 2021), several notable events have happened that don’t make this worth maintaining for me:
oklab() / oklch() landed in all browsers
This is now supported in CSS in all major browsers (~86% as of Jul 2023) 🎉. There’s no JS tool that compete with a built-in CSS feature. Why use an npm package for something the web platform gives you for free?
color-mix() landed AND supports Oklab mixing
Mixing colors through Oklab via
color-mix()
is now supported in CSS in all major browsers, and is safe to use in web projects today.Culori also got Oklab support
Culori added Oklab/Oklch support, and if you use the “tree-shakeable” version of
colori/fn
, you can basically get the footprint ofbetter-color-tools
at only a few kB gzip, but with a more stable library and support for more options.Oh, and did I mention
culori/fn
is a whopping 5-10× faster than this library for the same package size? 🚀🚀🚀Frankly, I don’t have the resources to try and tune better-color-tools to be that fast.
All of the above are developments I have welcomed, and couldn’t be happier for 🙂. But it’s made maintaining this library not worth the effort.
Though I considered the possibility of this library simply wrapping culori/fn, I’m not going to do that. Because creating unnecessary abstractions don’t make a good npm package.
Thanks to all those who tried this library and liked the API. But migrating to
culori/fn
for all your color needs will not only yield a better experience; you’ll also be contributing to better color science tools. And in the end, that’s what matters. 🎨The text was updated successfully, but these errors were encountered: