Skip to content

Commit 94c64be

Browse files
authored
Added more notes to Tailwind comparison.
1 parent b75583f commit 94c64be

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

README.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -47,9 +47,10 @@ Or, 🌐 CDN: `<script src="https://cdn.jsdelivr.net/gh/gnat/css-scope-inline@ma
4747

4848
Use whatever you'd like, but there's a few advantages with this approach over Tailwind, Twind, UnoCSS:
4949

50-
* No [repeat styles](https://tailwindcss.com/docs/reusing-styles) on child elements (..no [@apply](https://tailwindcss.com/docs/reusing-styles#extracting-classes-with-apply), no `[&>thing]` on each style).
51-
* No endless visual noise on every `<div>`. Use a local `<style>` per group.
52-
* No difference in syntax between local and global styles. Universal CSS.
50+
* No [repeated styles](https://tailwindcss.com/docs/reusing-styles) on child elements (..no [@apply](https://tailwindcss.com/docs/reusing-styles#extracting-classes-with-apply), no `[&>thing]` on each style).
51+
* No repeated prefixes for media queries, hover, focus, etc.
52+
* No visual noise on every `<div>`. Use a local `<style>` per group.
53+
* Share syntax between local and external styles. It's just CSS.
5354
* Regain your "inspect, play with styles, paste" workflow in your web browser!
5455
* No suffering from lost syntax highlighting on properties and units.
5556
* No high risk of eventually requiring a build step.

0 commit comments

Comments
 (0)