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.
In standup, and the boss mentioned an article called The Dao of Web Design, written by some wunderkind named @johnallsopp. This article tells you all you need to know about React and Tailwind! https://alistapart.com/article/dao/
#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).
Got annoyed trying to get the layout and design of a document correct in word processing programs (and it would ultimately be a #PDF when I saved / exported it) so I decided to just write it in #HTML and #Tailwind#CSS and then use the browser's print to PDF functionality instead and it worked a treat.
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!
I just argued today why I think that IN MY OPINION #tailwind is absolute trash and no fun to work with in pretty constructive argument I had.
I shared @heydon thoughts on this topic and my opponent how the Tailwind CEO feels about it. Clearly the article I shared won the argument (in my opinion):
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!”
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…