Re:Show HN: Flyon UI – Tailwind Components Library
by littlestymaar on Thursday October 03, 2024 @09:51AM
(#41730807)
> freedom from having to name things prematurely
> not having to jump back and forth between index.html and styles.css
Nobody prevents you to have your style directly in the HTML files (or in the JSX components, AKA CSS-in-js). Even though with split screen and keyboard shortcuts to switch I fail to see how this is an argument …
Re:Show HN: Flyon UI – Tailwind Components Library
by gr4vityWall on Thursday October 03, 2024 @11:45AM
(#41731794)
> Nobody prevents you to have your style directly in the HTML files (or in the JSX components, AKA CSS-in-js).
Why not just use Tailwind in your JSX components?
Re:Show HN: Flyon UI – Tailwind Components Library
by littlestymaar on Thursday October 03, 2024 @05:19PM
(#41735122)
> Why not just use Tailwind in your JSX components?
That just is out of place here: using tailwind means using inline style + having a CSS stylesheet (tailwind's stylesheet) at the same time. It's pure overhead.
Re:Show HN: Flyon UI – Tailwind Components Library
by gr4vityWall on Friday October 04, 2024 @12:03PM
(#41742764)
I don't know, feels more natural to me. Tailwind was a godsend.
- fine-grained design tokens (p-63 doesn't exist)
- freedom from having to name things prematurely
- not having to jump back and forth between index.html and styles.css