Earlier quoted context omitted.
Once you know the syntax of CSS properties you can jump into any codebase and instantly know what’s going on. With Tailwind you’re forever jumping between components and figuring out what that one long line of class names is actually doing.
> With Tailwind you’re forever jumping between components and figuring out what that one long line of class names is actually doing. Only if you already have no clue what CSS is. If you know CSS and can’t figure out what a given tailwind class does, then I don’t know if anyone can help you. That said, I do often feel that I might as well just write the css directly. Writing tailwind feels like another translation lay…
Konsta UI – Mobile UI Components Built with TailwindCSS
151–160 of 243 posts
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#152Earlier quoted context omitted.
Funny, to me arguing for Tailwind is like arguing for copy pasting code around instead of using functions and classes, which the Tailwind devs literally tell you to do by the way. I mean, when I saw their official recommendation for maintenance of code and reusing styles was to use multiple cursors , I had to laugh out loud. https://tailwindcss.com/docs/reusing-styles
No it's more like functional programming with small, single-purpose elements. Semantic CSS is more like object oriented programming with big bloated classes with poorly designed and leaky abstractions.
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#153Earlier quoted context omitted.
Should also read the reply then: https://twitter.com/adamwathan/status/1613718281969635328 The only people I know who dislike tailwind are those who either have never used it to make a project because of bias (hello past me) or those who dislike having faster development speed. Tailwind objectively saves time, yes, objectively.
I read most of the replies to the tweet I linked, including Adam's. It's simply not compelling enough for me to use Tailwind.
There are many alternatives. Move on, and stop getting upset with people who find it incredibly helpful.
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#154Earlier quoted context omitted.
That's all well and good until you have to maintain it at scale. I'd rather take regular CSS.
I guess you missed the part where I said I have used it successfully on several large codebases?
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#155Earlier quoted context omitted.
It's not my thing, I didn't make it, for one. Then just use CSS at that point, it's been here 20+ years then. I simply don't understand how it can be superior to regular CSS in any way simply because it maps one to one onto CSS properties anyway.
I do bare CSS for quick POCs but never on real projects. Vanilla JS & CSS sounds romantic when you solo but in a team setting it's better to use something we're all familiar with. At work we switched over from SCSS modules+global styles to Tailwind last year and it has been great so far: 1. No more custom CSS. No need to think how to name your classes. No more unused CSS. 2. Code completion (VSCode plugin for TW clas…
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#156I'm trying not to be a hater but really how is this: https://github.com/konstaui/konsta/blob/master/src/shared/cl... better than css or even css in js
It is not. But it's not like you write css like this this when you write tailwind. People use tailwind along CSS. You can write CSS components (written in css) and use them in tailwind and with tailwind. I am heavy tailwind user and when i see this it seems to me like people forgot css exists.
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#157Earlier quoted context omitted.
I read most of the replies to the tweet I linked, including Adam's. It's simply not compelling enough for me to use Tailwind.
Then don't use it. I doubt that anyone is forcing you to. There are many alternatives. Move on, and stop getting upset with people who find it incredibly helpful.
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#158Earlier quoted context omitted.
I guess you missed the part where I said I have used it successfully on several large codebases?
So have I. So now who's anecdotal evidence wins? It really is what it comes down to, isn't it?
Some people like Tailwind and find it incredibly helpful.
Some people don't.
Some people actively despise Tailwind.
No one has to 'win'. All these opinions can coexist.
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#159Earlier quoted context omitted.
Also, you can find a lot of Tailwind templates/components and they just work. You don't have to worry about a snippet clashing with or overwriting some other CSS you have like you would with plain HTML/CSS snippets. Sure, HTML looks uglier when I add a dozen classes to an element instead of adding one class with a dozen of CSS rules, but I'm more than willing to accept that as a compromise. Overall, Tailwind made fro…
I find that some people are upset by the "democratization" aspect of this honestly. It usually comes out as commentary along the lines of "well what's so hard about learning when to use !important?", "that tells me your CSS is poorly organized"... or sometimes just a drive-by downvote In my experience that comes from a misguided idea that people who jump at it are somehow uncurious, or irresponsible, for "wanting the…
I'm not. I have no interest in learning more, same way as frontend developers have no interest in learning to build custom Dockerfiles or Kubernetes deployments. It's not that it's difficult to pick up, we just can't be bothered to. People that do frontend just want their things to run, and I just want to be able to make a website that doesn't look like shit without spending a ridiculous amount of time on it.
Anything that bridges these gaps is a win in my book. Tailwind is better than Bootstrap (granted, it's been years since I've last tried it), better than drag-and-drop website builders, worse than pure CSS if you know what you're doing. It won't make your job obsolete, it just makes things easier for the rest of us. Same goes for docker-compose.
Re: Konsta UI – Mobile UI Components Built with TailwindCSS
#160Earlier quoted context omitted.
I guess you missed the part where I said I have used it successfully on several large codebases?
So have I. So now who's anecdotal evidence wins? It really is what it comes down to, isn't it?
Of course you can build big things with semantic CSS. You also can with Tailwind.