4 ms·
I don't get tailwind at all. I never pressed the play button in terms of the article, but it's like promoting the use of MS Word without formatting styles... Yo
by chromanoid 3y ago
I don't get tailwind at all. I never pressed the play button in terms of the article, but it's like promoting the use of MS Word without formatting styles... You end up with masses of shitty documents formatted with a wild mix of overlapping formatting options and extra spaces.
And yes, I am looking at you, Mom... ;)
- ramenmeal 3y agohttps://tailwindcss.com/docs/reusing-styles https://tailwindcss.com/docs/reusing-styles
- chromanoid 3y agoThat seems to be even more horrible than I expected, multi-cursor editing, seriously? @apply and the frowned upon solution is what I would expect to be the only clean solution. I am a proponent of WET, but pulling the naming things card when it comes to places that you may want to localize, test or aria-label anyway, just seems lazy to me.
- akarlsten 3y agoIn my experience there is practically no need to use multi-cursor editing if you're extracting components or partials where appropriate, as is usually the case nowadays. There's also a difference between naming things of actual significance, which as you say may need to be localized, labeled, etc. and having to name arbitrary CSS junk like .button--state--success, which is painfully annoying. Type it up in the CSS file, switch over to the markup file (another annoyance that Tailwind helps you avoid), paste it in, repeat.
- emmacharp 3y agoWhy wouldn't `.button.is-success` be enough? And aren't you already using `success` somewhere else in your component? In JS, maybe?