2022-09-22
3741
#css#web design
Obinna Ekwuno
818
Sep 22, 2022 ⋅ 13 min read

Comparing Tailwind CSS to Bootstrap: Is it time to ditch UI kits?

Obinna Ekwuno Writer of all things technical and inspirational. Developer and Community Advocate. In a love-love relationship with JavaScript🔥

Recent posts:

Hand holding purple sticky notes for CSS sticky positioning guide.

Troubleshooting CSS sticky positioning

Fix sticky positioning issues in CSS, from missing offsets to overflow conflicts in flex, grid, and container height constraints.

Ibadehin Mojeed
Nov 13, 2024 ⋅ 5 min read
Task Scheduling and cron Jobs in Node Using node-cron

Scheduling tasks in Node.js using node-cron

From basic syntax and advanced techniques to practical applications and error handling, here’s how to use node-cron.

Godwin Ekuma
Nov 12, 2024 ⋅ 7 min read
Working With The Angular Tree: Flat Vs Nested Trees And More

Working with the Angular tree

The Angular tree view can be hard to get right, but once you understand it, it can be quite a powerful visual representation.

Lewis Cianci
Nov 12, 2024 ⋅ 21 min read

Why you should use SWC (and not Babel)

In this post, we’ll compare Babel and SWC based on setup, execution, and speed.

Kasra Khosravi
Nov 12, 2024 ⋅ 9 min read
View all posts

13 Replies to "Comparing Tailwind CSS to Bootstrap: Is it time to ditch UI kits?"

  1. Need to update your code in the first example. `bg-purple` and `bg-purple-dark` no longer exist. Try `bg-purple-600 hover:bg-purple-800`

  2. “Another advantage I really appreciate — and I am sure every front-end developer would also appreciate — is never having to worry about changes to one element affecting another related element.”

    So if I change a component I need to change all other components manually to keep my layout consistent? That sounds really cumbersome and I don’t see how this is an improvement.

  3. Hey Bas!
    You have two basic choices for repeated elements here:
    1. use @apply in your CSS and build up your own class es for repeated components
    2. use Vue-, React- or PHP-Components and just include them whereever needed.
    It’s not too bad, for elements that lie beyond direct control, like WordPress’ WYSIWYG-Fields I just wrap that in a content class and use apply to style elements in there.

    Cheerio.

  4. Also for Bas,

    It can also depend on where you want to put your eggs.

    Do you want components you can guarantee won’t be effected or broken over time with a maximum css file size.

    Or do you want to update a handful of classes in the off chance your design requirement might change half way through. Which even if it does change, you get the benefit of not breaking other components by changing your design requirements 🙂

    People often forget that other programming languages apply the styling directly to the elements rather than global style sheets, so if it works for them! Can work for you

  5. Have you written inline css in your dom element? Tailwind is something like that in the form of classes. Its makes your dom element dirty with too many classes. And for similar kind of components writing little classes is far more better than writing many classes again and again.

  6. This article feels like a very opinionated and honestly can’t see any real points why Tailwind is better than Bootstrap. First, can you define what do you mean by saying “UI kit”? Bootstrap has prebuilt templates but that is up to you to use it or not, it provides responsive classes too like Tailwind if you need to have more control over what you are building. So having prebuilt templates and all what Tailwind provides I would go with Bootstrap any time. Just because Tailwind is new does not make the case, COVID-19 was new too, but no one liked it since it took a few years from our lives.

  7. Talk about re-inventing the wheel. Bootstrap has the exact same utility classes and more and yet people ignorant of these think they’ve stumbled on the holy grail.

Leave a Reply