headlessui VS flowbite

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

HeadlessUI : The library is only the headless part or behaviors you need to build accessible components. It is specifically designed to integrate with Tailwind, but you could use any CSS solution you like.

These depedencies provide unstyled accessible components from headless ui, icons from heroicons and common hooks with typescript support.

I created an ASP.NET component framework (Razor/Blazor) and used it to port HeadlesssUI (https://headlessui.com) components.

As devs, you might think of the term “headless” and your first association might be “headless components”, which are probably registered in your brain as components that only have an API and no UI. What I mean are projects/libraries like Headless UI, RadixUI, Downshift, TanStack Table, or a slew of others I might be forgetting.

I'm currently working on a project where I need to implement a Google Places autocomplete input. I've created a component called PlacesAutocomplete that uses the [use-places-autocomplete]([https://www.npmjs.com/package/use-places-autocomplete) and [headlessUI](https://headlessui.com) packages. The component encapsulates the logic for this feature fine, however, I'm facing difficulties integrating it into my form.

I do constantly use Tailwind classes to style me website. To up til now I don't remember using any of Tailwind libraries. Didn't even use them for my clients. I did however use https://headlessui.com/ to make some frequently used components much easier.

As we did with the modal video component created in a previous tutorial, we will use the Headless UI library for managing transitions. So, if we haven’t already, we need to install the library using the command npm install @headlessui/react@latest.

We will accomplish these two tasks in a single step by using a transition component. We’ll use the Headless UI library instead of Vue 3’s built-in Transition component. If you’ve followed our previous tutorial on creating a video modal component, you might already be familiar with this preference.

Flowbite is another popular and open-source UI component library that is based on Tailwind CSS and can help you build websites even faster where you can leverage elements like dropdowns, modals, navbars, and more.

Flowbite: Components on top of Tailwind for not only JavaScript frameworks like React, Qwik, Vue, Svelte, Angular, and SolidJS, but also for popular meta frameworks such as Astro, Next.js, Remix, Nuxt, Meteor, and non JS frameworks such as Laravel, Symfony, Ruby on Rails, Pheonix, Django, and Flask.

Flowbite

I was going to exclusively use DevExtreme for the entire UI, but I really, really like Tailwind CSS, so I think I'm going to use DevExtreme for the tables, filtering, and charting, and for the rest I think I might use something like Flowbite.