How can you write something so compelling when I've put so much effort to get semi-comfortable with Tailwind?! 😉
It's often so long between the projects where I use Tailwind that I'm constantly on their docs (they are great by the way). But it's adding an extra step for me. I know how to do something in CSS but I'm using the docs to find what the utility class is for what I want to do. I've been most happy styling when I've used SASS modules. But it's no denying that regular CSS variables are greatly appreciated!
Thanks for the write-up! I'm gonna stare into the mirror for a bit and see if I'll just yeet a dependency where regular CSS makes more sense 🤔
No, I think the post raised some valid points. Sure, it's good knowing such a popular tool as Tailwind because I encounter it in other projects. But for myself, it doesn't really speed up my development and SASS modules are a good way to manage my styles, making it easy to maintain over time.
Still, I like what Tailwind has done for me. I started using it at a time when I had terrible style structure. It was a horrible jungle in style.css. Tailwind was a gust of fresh air and made my styles a bit more maintainable in comparison.
It really didn’t. It was just a post to crap on Tailwind to sell the OPs Pollen framework.
Utility based CSS is valuable to understand and if you haven’t grokked it yet then continue. Sass based components still have issues with cascading and naming etc.
Just because Utility CSS (like Tailwind) has limitations doesn’t mean it isn’t valuable or “bad” and needs to be replaced with yet another framework that the OP is trying to sell.
How can you write something so compelling when I've put so much effort to get semi-comfortable with Tailwind?! 😉
It's often so long between the projects where I use Tailwind that I'm constantly on their docs (they are great by the way). But it's adding an extra step for me. I know how to do something in CSS but I'm using the docs to find what the utility class is for what I want to do. I've been most happy styling when I've used SASS modules. But it's no denying that regular CSS variables are greatly appreciated!
Thanks for the write-up! I'm gonna stare into the mirror for a bit and see if I'll just yeet a dependency where regular CSS makes more sense 🤔
Ignore the post. Stick to tailwind if you’ve been learning it.
No, I think the post raised some valid points. Sure, it's good knowing such a popular tool as Tailwind because I encounter it in other projects. But for myself, it doesn't really speed up my development and SASS modules are a good way to manage my styles, making it easy to maintain over time.
Still, I like what Tailwind has done for me. I started using it at a time when I had terrible style structure. It was a horrible jungle in style.css. Tailwind was a gust of fresh air and made my styles a bit more maintainable in comparison.
It really didn’t. It was just a post to crap on Tailwind to sell the OPs Pollen framework.
Utility based CSS is valuable to understand and if you haven’t grokked it yet then continue. Sass based components still have issues with cascading and naming etc.
Just because Utility CSS (like Tailwind) has limitations doesn’t mean it isn’t valuable or “bad” and needs to be replaced with yet another framework that the OP is trying to sell.
Like, you don't have to try that hard. You love tailwind, that's fine.
No trying. Just don’t like posts trying to sell their framework. I use Sass and bootstrap grid at work just fine.