←back to thread

Vanilla JavaScript support for Tailwind Plus

(tailwindcss.com)
304 points ulrischa | 3 comments | 25 Jul 25 18:11 UTC | HN request time: 0s | source
Show context
ricardobeat ◴[25 Jul 25 22:13 UTC] No.44689124[source]▶

    <el-dialog-panel class="mx-auto block max-w-3xl transform overflow-hidden rounded-xl bg-white shadow-2xl ring-1 ring-black/5 transition-all group-data-closed/dialog:scale-95 group-data-closed/dialog:opacity-0 group-data-enter/dialog:duration-300 group-data-enter/dialog:ease-out group-data-leave/dialog:duration-200 group-data-leave/dialog:ease-in">
Lovely. Verbosity aside, now on top of knowing CSS you need to learn another hierarchical system within class names.
replies(14): >>44689142 #>>44689193 #>>44689633 #>>44690309 #>>44690466 #>>44690969 #>>44691000 #>>44691208 #>>44691531 #>>44692110 #>>44692147 #>>44692803 #>>44694185 #>>44700048 #
1. gnarbarian ◴[26 Jul 25 03:02 UTC] No.44690969[source]▶
We need a total and complete stop to all front end development until we figure out what the hell is wrong with them.
replies(1): >>44691202 #
2. yoz-y ◴[26 Jul 25 04:01 UTC] No.44691202[source]▶
Some people (I suspect a lot of young and motivated developers) think that UI development should be easy and elegant.

But consider that a UI is 100% state management and side effects (so fundamentally imperative and asynchronous). On top of that it takes about three revisions for any tool to require bespoke display of something (everybody has an opinion). They also bring a layout engine which is best expressed in constraints.

And somehow we are trying to shoehorn all this into a functional paradigm.

replies(1): >>44691399 #
3. pjmlp ◴[26 Jul 25 04:43 UTC] No.44691399[source]▶
Mostly is, with native toolkits, Web should have stayed for hypermedia documents, but here we are.

I have used and programmed enough kinds of UIs, since I got coding into that Timex 2068 in 1986.