# Why Tailwind CSS Won - Matt Rickard Synced: [[2023_11_30]] 6:03 AM Last Highlighted: [[2023_08_19]] Tags: [[Software]]  ## Highlights [[2023_08_19]] [View Highlight](https://read.readwise.io/read/01h8603rgec4s04x9ee3d9sp6a) > • **No context switching from application logic.** The tagline on the website reads, *“Rapidly build modern websites without ever leaving your HTML.”* That’s partly true, but few developers are writing HTML (instead, they are writing JSX or TSX). Switching to a CSS file to change styles is a costly context switch. Instead, developers write CSS as utility classes right in their application. This also vastly simplifies complex CSS build pipelines (which rarely worked). > • **Copy-and-pastable.** Bootstrap provided templates that were easy to get started with. It became the de facto landing page for any side project or new startup. But designs weren’t copy-pastable. Doing so would require you to copy the CSS and HTML. Instead, TailwindCSS is supremely easy to copy — everyone works with the same utility classes, so you can just copy and paste a list of classes or an HTML block into your application, and it should just work. The same was true for bootstrap, the problem with bootstrap was the level of customizability, preferring configuration to composition. In some sense, configuration is easier, but it also leads to something feeling the same as other sites [[2023_08_19]] [View Highlight](https://read.readwise.io/read/01h8607424ertjync4dycygcdg) > Tailwind is tree-shaken by default Eh, the way that it goes about this seems backwards. It should learn something from UnoCSS instead and not tree shake, but just don't generate