Foolish of me to think "HTML-first" meant it wouldn't require nodejs/npm and that dependency hell.
HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
131–140 of 193 posts
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#132Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#133Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#134> framework-agnostic > Franken UI is a Tailwind CSS plugin :|
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#135Earlier quoted context omitted.
Yeah I know it’s crotchety old man territory but I find CSS absolutely fine to work with these days, now that we have variables etc. Every time I’ve added PostCSS, Tailwind or whatever I’ve found my build times jump a ton and I don’t get a whole lot of use out of it. Plain CSS and containerisation provided by Svelte (or the forthcoming scope stuff) is more than enough for me.
CSS is a dream these days. I understand why it’s intimidating for devs because it’s not meant for engineers it’s meant for designer so it has a wildly different set of assumptions and expectations. But learning it is 100% worth it. Tailwind is like an ORM. I get the appeal but if you know SQL /CSS it’s just going to get in the way.
SQL - Backend - Frontend - CSS
Most people just want to stay in the middle doing backend/frontend ("full-stack") work because it's just writing functions. Or because it's building the core of a feature, where things like database work and styling is pushed off or abstracted in libraries.But on each end is where all the interesting stuff is really happening, and a full-stack dev who embraces both SQL and CSS is a lot more useful than a full-stack dev who stays in the middle.
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#136> framework-agnostic > Franken UI is a Tailwind CSS plugin :|
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#137Earlier quoted context omitted.
Yeah I know it’s crotchety old man territory but I find CSS absolutely fine to work with these days, now that we have variables etc. Every time I’ve added PostCSS, Tailwind or whatever I’ve found my build times jump a ton and I don’t get a whole lot of use out of it. Plain CSS and containerisation provided by Svelte (or the forthcoming scope stuff) is more than enough for me.
CSS is a dream these days. I understand why it’s intimidating for devs because it’s not meant for engineers it’s meant for designer so it has a wildly different set of assumptions and expectations. But learning it is 100% worth it. Tailwind is like an ORM. I get the appeal but if you know SQL /CSS it’s just going to get in the way.
Sometimes I just wanna work on my app and not write css.
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#138But it's always good to have other options like this one.
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#139How about some color? Or in other words, how much longer until the Vercel-inspired brutalism fad wears off?
Re: HTML-first, framework-agnostic implementation of shadcn/UI – franken/UI
#140This is definitely not HTML first, though. This is TS first, JS second, CSS third, and only then, HTML last. I'm all for clean frameworks, but this is very far removed from the idea of putting HTML first.