Colour VS headlessui

Colour Science is one of the more serious projects I know of, and more or less lets you get as advanced as you want. Used by film professionals among others. https://www.colour-science.org/

How would you define what the perfect color tool is? I would guess like most tools that it depends entirely on the job at hand, and that maybe no one perfect tool can exist. Colour Science might be great at serious color management and perceptual measurements and conversions between standardized color spaces, but not the right tool for a web developer looking for quick & easy way to make an HSV palette generation widget (and not because Colour Science is Python, but because it’s too big and heavy of a hammer).

If you're using a DCI-P3 (wide-gamut HDR) display, then #0000ff (or #aaaaff) in that display's colour space will be emitted as more saturated blue light than what an sRGB display is capable of. I am not sure if you will perceive them as exactly equally bright, brightness is subjective and depends on the reaction of your retina to the light hitting it, which is why #0000ff (blue) appears darker than #00ff00 (green), however the objective energy of the emitted light should be equal between displays of different gamuts, i.e. #ff0000, #00ff00, #0000ff should all result in the same amount of light being emitted in every correctly calibrated display regardless of the RGB primaries (aka gamut) it uses. The whole colour space topic is pretty deep, if you want to learn more about it and how colours are represented and converted between spaces, I encourage you to go and check out https://www.colour-science.org/ and linked resources.

People that work on resolve also work on https://github.com/colour-science/colour which is most REFERENCE code and complete support there is.

I haven’t seen the math for the conversion but the conversion from CCT to xy/uv are given for a particular domain. One of the conversion with the largest domain, i.e. Ohno m, covers domain [1000K, 100000K]: https://github.com/colour-science/colour/blob/develop/colour...

Infinity is very much in extrapolation territory.

I did a little digging and it's this one https://github.com/colour-science/colour/issues/666

Catalyst is a comprehensive, fully componentized UI kit for modern React projects, built on the next generation of Headless UI. With Catalyst, you can create a custom set of components to use and reuse in your projects.

And that is why I was looking for a UI library that would deliver these things for a long time and today I am happy to announce that I have found it! It is Headless UI by the Tailwind Team.

Headless UI provides a suite of unstyled, fully accessible UI components perfect for developers who want full control over their interface design. It's a developer's canvas, offering the foundational parts needed to build a user interface without dictating the aesthetics, making it ideal for those who love to integrate with Tailwind CSS. With https://headlessui.com/, you can ensure that your applications are inclusive and easy to use for everyone, while also maintaining the freedom to craft a unique look and feel that aligns with your brand or style guidelines.

GitHub stars: 22.5k GitHub link: https://github.com/tailwindlabs/headlessui Documentation: https://headlessui.com/

Website: Headless UI

Few months ago, I discovered project called Headless UI and I instantly liked the idea.

In addition to Tailwind CSS, Tailwind Labs also created Headless UI, a collection of components that work well with Tailwind CSS.

Tailwind - Headless UI

Thanks for sharing! I love projects that reimagine entire ecosystems: there's a lot of value in imagining what could be if we didn't worry about what is.

Some feedback: your comparison of the various ListBox implementations[0] feels disingenuous. I know Vue best, so I looked at that implementation in detail, and it's got a lot going on that you don't attempt to replicate in your version. A few key features that are missing:

* Search—in the HeadlessUI version there are several hundred lines dedicated to making typing work for jumping to specific list items.

* Multiselect—HeadlessUI supports multiple selections, yours does not appear to. Again, this occupies a lot of lines.

* Focus management—HeadlessUI has a lot of code dedicated to smoothing out the focus management. In my testing, your implementation has pretty buggy support for using tab to navigate.

* The HeadlessUI version dedicates a lot of lines to types, where your Nue implementation is dynamically typed. This may be a feature for you, but in my mind those type declarations are doing important work.

* In general, the HeadlessUI implementation tries to be flexible for many use cases [2], while yours only needs to support the one demo list.

You also include this render.ts file [1] from HeadlessUI, which is more part of a bespoke sub-framework used by HeadlessUI than it is a necessary part of any old Vue ListBox implementation. If you're going to count that against Vue, then there are parts of Nue JS that should be included as well.

These kinds of comparisons are most persuasive if you can write all the implementations from the ground up, using idiomatic patterns for each framework and identical feature sets for each implementation. When you do that, it's easy to compare and contrast the frameworks. As it is, it's like comparing a house to a garden shed: yes, you've used fewer lines of code, but it's not obvious to me that that's a feature of Nue and not just a byproduct of a less ambitious component.

[0] https://nuejs.org/compare/component.html

[1] https://github.com/tailwindlabs/headlessui/blob/%40headlessu...

[2] https://headlessui.com/vue/listbox#component-apihttps://head...