Working with Tailwind CSS every day for 2 years
themosaad.com
Working with Tailwind CSS every day for 2 years
1–10 of 215 posts
Re: Working with Tailwind CSS every day for 2 years
#2Nice to see this on the front page at the same time that a negative about Tailwind article pops up. Especially since I'm currently looking at whether to start using Tailwind. It's good to read multiple, conflicting, opinions about something.
Re: Working with Tailwind CSS every day for 2 years
#3I don't like Tailwind, except for pure layouting where it truly shines. My belief is this: we should think of layouting and styling as two distinct concepts and it doesn't help that CSS is used for both. After years of experimenting with various CSS approaches, I believe using Tailwind for layout and styled-components for styles is the ultimate setup for React applications.
Re: Working with Tailwind CSS every day for 2 years
#4I have been working with HTML since I was 11 — 20ish years. I thought I knew most things. text-decoration-thickness? Nope. I have been adding border-bottom to spans for far too long it looks like.
Re: Working with Tailwind CSS every day for 2 years
#5I have been working with HTML since I was 11 — 20ish years. I thought I knew most things. text-decoration-thickness? Nope. I have been adding border-bottom to spans for far too long it looks like.
Those are pretty new. text-underline-offset is another one that made my "fake" underlines obsolete
Re: Working with Tailwind CSS every day for 2 years
#6I don't like Tailwind, except for pure layouting where it truly shines. My belief is this: we should think of layouting and styling as two distinct concepts and it doesn't help that CSS is used for both. After years of experimenting with various CSS approaches, I believe using Tailwind for layout and styled-components for styles is the ultimate setup for React applications.
How do you distinguish what is "layout" versus "style"?
I know there are some obvious things, but like you said CSS is used for both. So there is a lot "grey area". Especially when "style" can affect the "layout".
Re: Working with Tailwind CSS every day for 2 years
#7Does that blog have an RSS feed?
Re: Working with Tailwind CSS every day for 2 years
#8Slightly off topic, but you can chain your language selectors in VS Code settings so that:
"[javascript]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[typescript]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[javascript][typescript]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
}Re: Working with Tailwind CSS every day for 2 years
#9I'll be honest here, after working with tailwind for 7 months I really hate this piece of tech and really regret picking this company.
I thought it wouldn't be a big deal but after seeing unnecessary long walls of class names I'm really tired. Anything other than basic styling is an absolute pain with tailwind and I don't understand why /my company specifically/ can't just use typestyle/styled-components/css modules to separate walls of text from components. With time, I degraded to the point I where I use classnames library just to split longer class string into 3-4 smaller ones so I can split the component into multiple rows to make it look better
Re: Working with Tailwind CSS every day for 2 years
#10I have been working with HTML since I was 11 — 20ish years. I thought I knew most things. text-decoration-thickness? Nope. I have been adding border-bottom to spans for far too long it looks like.
Those are pretty new. text-underline-offset is another one that made my "fake" underlines obsolete
Also remember text-decoration-style, text-decoration-color and text-decoration-skip - setting this last one to 'ink' will make the underline, ahem, skip over the glyphs with descenders, adding to legibility