@codewithvoid It's not a standard and can become a liability in the future.
@codewithvoid The sample on the landing page perfectly illustrates why I am not using it.
@codewithvoid I am way more comfortable with Plain CSS for now. Need to start using Tailwind CSS more🤔
@codewithvoid Because I don't like my HTML looking like a novelist wrote it
@codewithvoid Feels like being forced to build only flat-pack furniture when you have spent your career learning the craft of cabinet making. Or being a skilled Chef and having to work at McDonalds.
@codewithvoid Tailwind is for components and when you can't use preprocessors like sass scss, if you try to use on bigger projects you might get into a lot of trouble, and of course never let the junior create it...
@codewithvoid I want to master vanilla css before I jump to Tailwind.
@codewithvoid I am thinking of using it in my next projects. I am currently using SCSS with Flexbox and Grid. It's good, but I have grown tired of writing so many media queries.😅 Hope Tailwind helps me reduce the time it takes to write those...😅
@codewithvoid I honestly enjoy writing vanilla CSS, and I don't feel like I need any help with it. Sometimes, using frameworks and clever solutions just mess up your workflow rather than actually make you productive. Kind of how most todo-apps are smart but never simpler than basic txt files.
@codewithvoid Because utility classes are bad. CSS is advanced enough you don't need front-end frameworks anymore.
@codewithvoid Bro I love to write my own custom CSS love to modify it the way I want it to be, since I learnt CSS modules way back I'm in love with CSS. Btw what's your reason for hating CSS and what's your reason for loving Tailwind, also you know you're cheating on CSS right 💔.
@codewithvoid I enjoy writing plain CSS, tailwinds makes my code difficult to read with so many classNames, maybe I'm using it wrong way, idk
@codewithvoid We’re having a discussion on switching to Tailwind at GitLab. The discussion is public if you’re interested to see what our dev team thinks about it: gitlab.com/gitlab-org/fro…
@codewithvoid Why anyone WOULDN'T use tailwind is beyond me. Utility classes for gradient backgrounds 🙌 SOLD!
@codewithvoid For smaller projects, I don't feel the need to add a framework. Plus it is good to keep using it, so one doesn't forget.
@codewithvoid It creates miserably WET code. I mean, just unbearably so. The best bet is using variables to store the strings but even then it's a pain.
@codewithvoid Tailwind is obtrusive CSS. Tailwind does to html what inline JS was doing 20 years ago - it's a bad practice. I will die on this hill.
@codewithvoid Because ... - I can write CSS - The global nature of the CSS doesn't scare me - I learned to use methodologies that helps me maintain my stylesheets - Not every website follow a design system - I prefer to keep my workflow simple
@codewithvoid Tailwind makes your classNames long like River Nile.
@codewithvoid because Chakra Ui with React is just a breeze, you compose your UI with ease
@codewithvoid I'm yet to hear an argument for things tailwind lets me do that I can't already do with CSS.
@codewithvoid Probably new to web development 🧐
@codewithvoid With large html/template files it starts to get too much chaos. I appreciate Tailwind, I know there are situations where it is worth using it. But it happens in my work very rarely
@codewithvoid Good: - It helps me visualize the style directly where I write it - Generate only the necessary CSS - Good defaults but it is also very customizable - For me, it's easy to read Bad: - Installing it can sometimes be frustrating without libraries like github.com/timonweb/djang…
@codewithvoid Bootstrap is (also) fine if you need a framework. Much can be achieved using CSS alone though, without taking a dependency on a 3rd party framework.
@codewithvoid I don't like how tailwind pollutes the main codespace. I prefer my css in a separate file as much as possible.
@codewithvoid For me, 3 reasons... 🔹I like full having control 🔹I don't like to clutter my HTML with tons of classes 🔹I try to avoid being too tightly coupled to frameworks because (1) I inherit their issues, & vulnerabilities, and (2) it hinders my ability to change frameworks later
@codewithvoid Quite simply, I haven’t needed it. I’ve either worked on projects with other frameworks in place, or the project hasn’t required the addition of a framework. If I’m involved in starting a new greenfield project where a css framework would be useful, I’ll consider it.
@codewithvoid It compiles a global stylesheet, and it's a one-way door - that is, a very opinionated, controversial, permanent decision.
@codewithvoid I love the new interaction of tailwind Css and the animation is great but I can do the almost the same thing with bootstrap 5 and bootstrap is just so easy... Just remember the class and a couple of concepts that are required to learn Bootstrap.
@codewithvoid It takes a lot of design decisions for you and this is the only solution that worth it's use. The other allegedly things that tailwind do are problems created by the tool itself