Live data from Hacker News

Show HN: Flowbite – Tailwind CSS Components Library

flowbite.com

51–60 of 60 posts

Re: Show HN: Flowbite – Tailwind CSS Components Library

#51

Earlier quoted context omitted.

Do the pro version allow re-use in templates?

Please read the full licensing terms for the pro version here: https://flowbite.com/license .

You pretty much copy pasted the Tailwind UI license word for word and replaced a few Tailwind UI-specific words with yours.

Components => download files

Tailwind UI components => FlowBite elements

Tailwind Labs Inc. => Crafty Dwarf LLC

Tailwind UI License: https://tailwindui.com/license

Flowbite License: https://flowbite.com/license/

Re: Show HN: Flowbite – Tailwind CSS Components Library

#52
post #5
post #4

Earlier quoted context omitted.

Doesn't look all that different from your own site: https://i.ibb.co/VWxZdhr/rado-bg.png

Actually, this here is semantic HTML. The previous example is not.

In which contexts would it matter whether one used article instead of div?

If you're on a screen, it makes no difference.

If you use a screen reader/braille display, you will only be informed about a small subset of "semantic" html elements, such as headings, lists, links, and tables.

If you think it matters for "XML" reasons, well, it's not 2006 anymore.

Re: Show HN: Flowbite – Tailwind CSS Components Library

#53
post #16

From a design perspective this looks really good, I like the components, the typography, the generated pages from Figma etc. Also the documentation seems to be clean and user-friendly. It's way better than most of the docs. From the development perspective and from other comments that are here, and also from many articles like: https://dev.to/jaredcwhite/why-tailwind-isn-t-for-me-5c90 or https://dev.to/neophen/tailwi…

TailwindCSS is the biggest jump in productivity for me in years.

I think where it shine most is when you are making your own UI and need to deploy different components/customizations, ie: If you are doing a single page site is not that obvious "why is like this?", but generating UIs on the fly for a admin backend and suddenly THIS IS THE WAY!.

TailwindCSS is like static types for UI. Note:

     == fn sum(a,b)

     == fn sum(a:U16,b:i32):Result
The "verbosed" nature of both cause some hate, but you will appreciate it the more big/complex the project is.

What you get with tailwind is exact understand of each component and how it will look based on their "types"/classes.

What you get with others like bootstrap is too abstract/implicit looks that you can't figure at a glance. So, tailwinCSS like static typed programming is optimized for "a glance"/local understanding.

What is also very counterintuitive is that my tailwind pages are LESS heavy than boostrap! (true for html and CSS)

Re: Show HN: Flowbite – Tailwind CSS Components Library

#54
post #23
post #19

Earlier quoted context omitted.

Interesting, I'd ask you why. Anecdotally I've built hundreds of websites, and worked on many product teams building web applications all with varying team/product sizes and in my experience BEM scales very poorly. I have never worked on a BEM codebase without a shocking level amount of tech debt. Adding new UI requires creating new CSS files, refactoring existing UI requires also refactoring the separate CSS files,…

Adding new UI requires creating new CSS files, refactoring existing UI requires also refactoring the separate CSS files, removing UI is the same thing. Due to this disconnect, old code tends to stick around. To me this says more about the development practices of that team than about BEM. Chiefly you should be able to automatically determine if a given block, element or modifier is still used/needed. How did they win…

Anyone who is still comparing Tailwind to inline styles in 2021 is probably not as experienced as they think they are.

Re: Show HN: Flowbite – Tailwind CSS Components Library

#55
post #40

Earlier quoted context omitted.

We keep all of our components in template files so it's quite easy to maintain for us. If we need to change all of the buttons across the app, we just update the Button component.

I also was using component tempalte files although the issue was apparent when returning to any component with any degree of complexity. Regular CSS class names tend to give you a bit of an insight into the role of each div whereas atomic css requires you to parse each line to understand it's role which gets a bit tiring after a while. I tried extracting the strings of atomic class names to variables as a sort of hyb…

IMO you can and should still add useful class/id names to explain what your elements are doing. Those just won't have any styling associated with them.

Re: Show HN: Flowbite – Tailwind CSS Components Library

#60
Guys, do you realize there are 12 classes to define 1 frickin default button? When all you need is btn btn-primary this tailwind CSS thing seems like a bunch of nonsense to me. Sure it's great to see a lot of ready made html components and it's tempting to just grab one and get a head start - and it might just work well for a landing page (I've used tailwind exactly for this) but for full blown applications? Using these components is just madness.
Post reply on HN