svelte-headlessui VS headlessui

Hi everyone, I'm so happy I can finally share the project I've been working on for the past few months. Ato UI is a themeable component UI library built with UnoCSS (with the Tailwind + Windi preset) and offers both styled and headless components, since the library is build on top of other fantastic headless libraries like Headless UI and Grail UI. Skeleton was also a big inspiration, as you'll be able to see in the designer page and the token system.

You mention YAGNI, but I think the bigger blocker is "Don't reinvent the wheel" - which I think is the most misunderstood bit of programming advice out there. In my SvelteKit app, I am not using a "UI Framework" that provides components to me. I don't need to. Svelte is simple enough that I can build almost anything myself. I've looked at Skeleton's source code, and their components on average are not better than versions I have rolled myself. There are a few cases where it's better to use a framework. Sliders, for instance, have a lot of edge cases. So I use Swiper for carousels. But even then, I could build a working basic slider (that doesn't address the numerous edge cases) myself in an hour. The other case is Headless UI but even there, I disagree with how he implemented some things and it's possible to roll your own Svelte Headless UI just from Tailwind's source.

I've been using https://github.com/captaincodeman/svelte-headlessui/ since previous with react I was using headlessui w/ tailwid.

I've also seen this alternative library utilising svelte use:action directive rather than components.

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...