Yeah. Okay.
Most of this was taken from another forum and mildly edited by me, but I consider it a generally accurate assessment…
The two technologies are not 1:1, and many folks don’t seem to understand the differences or similarities. For example, you have to pay (at last check) $300-$800 to gain access to the Tailwind component libraries & templates, while Bootstrap’s component framework is a dominant AND FREE feature that has been the go-to choice for developers over 10 years. That’s one of the reasons it’s the leader.
Bootstrap 5 dropped the jQuery dependency (which was a major pain point.) 90% of the utility classes that Tailwind offers have direct parallels in Bootstrap, they just aren’t grouped and described as a “utility framework”. So much of this is how things are bundled and branded.
Tailwind is typically a lot harder for the average user to set up.
However, the biggest difference between the two frameworks is the availability of tens of thousands of themes - free and paid - for Bootstrap, where no parallel exists for Tailwind. Bootstrap themes are a meritocratic cottage industry worth many millions, while Adam Wathan has structured Tailwind so that the only person making money is Adam Wathan. These two market models speak to the very different core demographics for each framework. Bluntly: Tailwind attracts geeks who are chill with spending the day tweaking PostCSS and think of their sites as a hierarchy of components with elements holding 20+ CSS classes, while Bootstrap is a huge success with designers and less technical bloggers and solo entrepreneurs who don’t mind forgoing some customizability to have a nice looking site out of the gate.
I’d hazard to guess that the typical Tailwind enthusiast wouldn’t buy a paid theme, even though they would be very sad if someone pointed out that their sites all look like programmers made them.
As for the total market size: it goes without saying that there’s more than enough opportunity for the two different approaches to coexist. I’d speculate that many Bootstrap devotees wouldn’t even consider Tailwind because their problems have already been long since solved by Bootstrap.
With this said, let’s look at Bootstrap vs Tailwind on Google Trends. Notably, the disproportion between the two is such that Tailwind’s impact on Bootstrap has been (and continues to be) little more than a rounding error.
https://trends.google.com/trends/explore?geo=US&q=%2Fm%2F0j671ln,tailwindcss
And finally, this is worth the read…
(Now cue the historical soundtrack)
As a graphic designer who started designing websites 20 years ago in Photoshop and handing them off to (then) HTML “wizards,” I will say this. In the post AOL world, when the web started to gain popularity among the masses, it was largely about finding and sharing information. UI and UX barely mattered. It was mainly the computer geeks’ playground. Ordinary people used the web to do research, share files and software, or for recreation - engaging in primitive social networking by exchanging pictures, flash animations, “surfing the web”, etc… (I’ll forgo mentioning the porn-colored elephant in the room.)
We had two basic devices to access the web - desktops computers and laptops - with two basic browsers - Netscape and IE (maybe Safari if you cared about the Apple crowd.) We designed for one or two screen resolutions. For most individuals who had their own websites, it was about making an artistic statement (usually, sadly, with dozens of animated gifs .) For most businesses, websites were glorified business cards or informational brochures. For designers, it was the “wild west.” Dramatic and unconventional was the rule of the day. If you made a website that looked different or did something nobody had ever seen before, that was a huge deal. But there was a LOT of ugliness on the web.
Then two things changed the entire game:
- e-commerce/advertising
- mobile devices (mainly smartphones.)
Number one changed the entire focus of what we used the internet for. It was no longer about sharing information, it was about making money (some may say, “but what about social media?” but social media is really just another way to advertise/make money.) Once money/commerce entered the equation, the bar had to be raised. Things had to become more professional. The wild west had to be tamed.
Number two ushered in responsive design, and the realization that websites had to be both visually appealing and functionally intuitive on countless devices. This meant standardization (something designers HATE.) It was a painful transition with some significant setbacks (remember Adobe Muse and Flash websites? ) It took awhile for us to settle on the basic format that is widely in use today, but standardization was necessary because we had millions of people discovering the web every month, and like automobiles (with steering wheels, gas pedals and brake pedals in the same locations) people needed websites to have predictability.
Frameworks were a huge step forward in this regard because they constrained developers to building websites in ways people expected them to look and work. The reason Bootstrap became so popular is not because it made it easier to build sites (although it did) but rather because it did an exceptionally good job in making websites look and work the way people expected them to.
Tailwind is not a revolution in web development. It doesn’t create “better” websites, and it’s not going to replace Bootstrap. It’s just another approach to how we use CSS. To an end user, there’s absolutely no distinction between a website built with Bootstrap and one built with Tailwind. A site built with either can be made to look and function exactly the same. Development tools will continue to evolve in minor ways, but until there is some major paradigm shift in what we use the internet for, the tools freelancers and small teams choose will largely be a matter of what each finds works best for them.
If you like Tailwind and it works best for you, then that’s what you should use. If you like Bootstrap and it works best for you, then that’s what you should use. Or you could use both. Or neither. At the end of the day, the only thing that really matters is the end-user’s experience.