Tailwind? Even their little TT code example on their home page is 100% cringe-worthy:
<div class="md:flex bg-white rounded-lg p-6">
<img class="h-16 w-16 md:h-24 md:w-24 rounded-full mx-auto md:mx-0 md:mr-6" src="avatar.jpg">
<div class="text-center md:text-left">
<h2 class="text-lg">Erin Lindford</h2>
<div class="text-purple-500">Customer Support</div>
<div class="text-gray-600">(555) 765-4321</div>
See all the presentational classes like text-gray, text-center, h-16, w-15, bg-white, etc, etc? See the INVALID class names with the MD: bs? See how every blasted element has a class for ZERO legitimate huffing reason? /FAIL/
at the most basic concepts of HTML and CSS, utterly undoing the twenty years of progress we've had since idiocy like <font> and <center> were deprecated. The very notion of using classes in this manner simply broadcasts to the world a failure to understand why CSS exists, how to use it, or why so many things were deprecated in 4 Strict.
Again, a poster child for the "3i" of web development; ignorance, incompetence, and ineptitude.
A likely contributor to why Tailwind's train wreck of a website is blowing 87k of markup to deliver 5.7k of plaintext and only two media elements -- not even 16k of HTML's flipping job. Tied to an ape-shit ridiculous 480k of CSS in three files when they don't even HAVE media targets...
When there is little legitimate reason for any competently coded SITE to need more than 48k in one file per media target FOR THE ENTIRE SITE!
Even just this:
<link rel="stylesheet" href="/assets/build/css/main.css?id=e994f5f9525b4219e81f">
<link rel="stylesheet" href="https://cdn.jsdelivr.net/docsearch.js/2/docsearch.min.css">
Is an epic /FAIL/ at web development due to a missing -- and very important -- attribute.
Of course being a front-end framework the fact that they want you to install via NPM? /FAIL/ at separation of concerns too.
This page alone:https://tailwindcss.com/docs/responsive-design
Being MORE than enough proof these clowns do NOT know enough HTML or CSS to be writing a single blasted thing client side... again with the PX media queries, presentational classes, DIV for nothing, DIV+classes doing numbered headings and SMALL's job, etc, etc, etc.
They've got this idiocy:
<img class="rounded-lg md:w-56" src="https://images.unsplash.com/photo-1556740738-b6a63e27c4df?ixlib=rb-1.2.1&ixid=eyJhcHBfaWQiOjEyMDd9&auto=format&fit=crop&w=2550&q=80" alt="Woman paying for a purchase">
<div class="mt-4 md:mt-0 md:ml-6">
<div class="uppercase tracking-wide text-sm text-indigo-600 font-bold">Marketing</div>
<a href="#" class="block mt-1 text-lg leading-tight font-semibold text-gray-900 hover:underline">Finding customers for your new business</a>
<p class="mt-2 text-gray-600">Getting a new business off the ground is a lot of hard work. Here are five ideas you can use to find your first customers.</p>
Doing the job of:
alt="Woman paying for a purchase"
<a href="#" >Finding customers for your new business</a>
Getting a new business off the ground is a lot of hard work. Here are five ideas you can use to find your first customers.
<!-- .describeThisCardType --></div>
Because if you're saying things like "rounded-lg" or "uppercase" or "font-bold" you have utterly and thoroughly failed to divine the entire reason CSS exists, why it's separate form HTML, what semantic markup -- A sick euphemism for using HTML properly
-- is for, and to be brutally frank has one's cranium wedged so far up 1997's rectum we'd need to call an orthodontist to handle the extraction.
You LITERALLY might as well go back to using FONT, CENTER, BGCOLOR, LINK, ALIGN, BORDER, with those TABLE for layout everyone so clearly seems to miss for piss knows what reason. All this idiocy does is recreate that same broken mentally challenged mentality with classes instead of tags and attributes.
As I've said a number of times and places, I do not think it is even possible to create a "front end framework" that isn't total incompetent and ignorant trash -- because how every blasted one of them works -- using classes to say what you want things to look like -- is the antithesis of proper use of HTML and CSS. Just like the halfwitted bald-faced lie that throwing classes at everything instead of leveraging selectors makes render "faster" or "easier". Since writing twice the code and handing twice the instructions to the browser is going to be better/faster/easier. Tell me another one Josephine.