This article uses #React as it's main example, but it applies to #Laravel, #Tailwind, even #Drupal just a much. I say that as a recovering Drupal dev who used to use the standardization argument.
Greedy management is the reason we can't have nice things.
Excited to share tailwindcss-fluid-font-size, a new fluid typography Tailwind plugin.
I’ve been iterating on Tailwind approaches to fluid typography for a couple years. tailwindcss-fluid-font-size is more flexible and, to me, the most ergonomic and idiomatically “Tailwindy” of the solutions I’ve built or read about.
Open minded Tailwind haters might even be interested in at least the design.
#nuejs looks way too ambitious to be taken seriously. I might be absolutely wrong tho. Also why does the creator keeps calling it "Perfect web framework" ? There is no such thing as "perfect" and you shouldn't resort to such "marketing" gimmick when you called out #tailwind for misleading marketing (still hate tailwind anyway)
Been slowly tinkering on a Litestar app I'm building just for the hell of it. My local amateur soccer league could really use a website, and I could also stand to learn a new web framework. (I mean, why not?)
While I've been plugging away at it (over-engineering and all), I decided to continue building in public.
Lots of fun stuff in here, but a pretty good "real world" use case for the PyHAT stack (htmx/Tailwind).
Tailwind vs Semantic CSS: "This study compares two sites with identical design: the commercial Spotlight template from the developers of #Tailwind vs the same site with semantic #CSS. The semantic version is 8× smaller, renders faster, and requires no JS bundlers/tooling." https://nuejs.org/blog/tailwind-vs-semantic-css/
"This study compares two websites with identical design: the commercial Spotlight template from developers of #Tailwind vs the same site with semantic #CSS."
My thought on the recent barrage of “#Tailwind#CSS is the antichrist! 🔥” posts
Animated slides. They read: I was there for # spacer.gif --- I was there for # Zen Garden --- I was there for # Responsive Web Design --- I was there for # flex and grid --- I’m there for # @layer, @container, and :has() --- # I still choose Tailwind --- ## You do you --- ## Don’t @-me
💜 Remix / Tailwind Infinite Scroll Masonry Grid 💜 So excited to have gotten this so smooth and beautiful. It might be my favorite component thus far. It is flawless from mobile to ultraHD, from 300px to 4000px!
This thread pretty much sums up my thoughts on #Tailwind:
While it can be useful for rapid prototyping, too often our prototypes get shipped as “MVPs”, which are then never given the space to really be cleaned up.
As a result, shit like this lives on and we continue the cycle of “front-end needs to be over-engineered so people will respect us!”
I always wondered why people writing #Tailwind all day are so aggressive. Especially if you don't want to use it.
Then I had to use Tailwind for a while. Now I understand. If I had to do this every day I would be aggressive too. And they probably just want someone who suffers with them.
I definitely will stick with #CSS. That sparks joy.
My guess is that both are clashing in the way they're setting style rules
My only question would be: if we're using Tailwind already, why are we using an opinionated component library like MUI anyways?
All the utilities and frameworks have been kind of decided on before I joined the team and if I ask to restructure the whole thing I'm gonna be met with rather stark opposition with some argument that will boil down to sunk cost fallacy :drgn_hide:
Failwind UI And The SPA Clown Shoes (HTML Illiteracy Part 4) (deathshadow.medium.com)
Single Page Applications, AJAX loading of content… there are legitimate reasons to use these technologies. That said I am constantly amazed…