I do things, with things. Sometimes virtually. Sometimes musically. Sometimes visually. Sometimes theoretically.
> The world is here to be understood, and a day without learning is a day not lived.
A developer with M.Sc. in Computer Science. Working professionally since 2010. In my free time I make music and cook.
Also I don't and after the recent events will not have Twitter.
Location
Budapest
Education
Eötvös Loránd University (ELTE - Budapest Hungary) Computer Science M. Sc.
At this point it feels like the Church of Tailwind gaslights people. It breaks many clean code basics like avoid mental mapping, yet we are told that this approach is cleaner and more efficient than writing normal CSS. It's for people who don't get that locally styling everything from zero is the polar-opposite of the design of CSS. Probably it's the same batch of people who tries to go full-OOP or full-FP in JS not understanding that, sadly, the design of the language will always break important details of either approaches.
Sometimes I feel like Tailwind advocates live in a weird fantasy world. So much stuff they say just doesn't seem to conform to reality, like when they say you need to know CSS to use tailwind correctly, or that it makes code cleaner, etc.
I think the main allure is maintainability and code confidence. If you're code isn't dependent on custom "named" classes then you never have to worry about breaking something somewhere else when making a style change. How many times have you changed a class style only to realize it breaks some implementation somewhere else in your app that you now need yet another custom class for though? To your point, no it doesn't make style declaration cleaner, it makes it so you don't have CSS files 1000's of lines long with 100's of unique classes defined that have maybe 1 or 2 property differences.
I'm not a Tailwind advocate but there are legitimate use cases where the philosophy behind Tailwind makes sense. For instance when an app gets too large to maintain any reasonable sense of where classes are applied and you're able to confidently say, "making this style change will only effect this scenario". Or, you have multiple people working on separate teams changing code on the same app. Is Tailwind pointless on a marketing website? Probably. Does it make your mark-up more complex and harder to read? Yes. When you're dealing with an application with 100's of features and UI components and multiple teams though... you'll trade the time it takes to read Tailwind for not having to account for class duplication or test, and fix, your changes to an existing class breaking a different implementation in the app.
the main allure is maintainability and code confidence
Saying that something is more maintainable and at the same time more complex and difficult to read (later in the comment) is contradictory. Complexity and difficulty to read make the code more difficult to maintain. What is it?
How many times have you changed a class style only to realize it breaks some implementation somewhere else in your app that you now need yet another custom class for though?
Almost none. To be honest, I can't remember having that problem at all. Following a methodology similar to BEM (not necessarily BEM) will avoid that problem completely. If your class is something like module-component-element, you will not get name conflicts and it will be easy to know what each class represents (both in HTML and CSS).
it makes it so you don't have CSS files 1000's of lines long with 100's of unique classes defined that have maybe 1 or 2 property differences
The CSS code generated by tailwind is literally CSS files with 1000s of lines of code with unique classes with just one property. You may not see how the sausage gets made, but it gets made anyway.
Don't take me wrong. Tailwind has good things: CSS code pruning which is great, the apply directive (discouraged by the authors), cross browser support (it adds vendor prefixes)... But I wouldn't list maintainability or small code as pros. I would consider them neutral or put the in the cons column.
👨💻 Professional problem solver - 🎧 Music lover
Hello! Thanks for checking out my profile.
If you haven't yet, make sure to also follow me on my other social media! ⬇️
Or as happened 3 weeks ago, client cancelled project after 4 months in prod, when it took 7 months to design and build! Oh well, I guess I still got paid.
👨💻 Professional problem solver - 🎧 Music lover
Hello! Thanks for checking out my profile.
If you haven't yet, make sure to also follow me on my other social media! ⬇️
I took up photography, it's creative, I get outdoors and I get to control how much or how little I use tech. I shoot film on landscapes, almost none. I shoot digital on architecture and I use loads, to the point I was writing Golang utils to get image meta data extracted
Let's get it going
Does this qualify as a meme? I thought it was funny 😃
Yes
Works for me 🤣
And it's awesome too!
longwalkwoodworking.com/catalog
Working in a regulated industry:
It's one character of code, what could it take, three months of change requests?
I've been picking on Tailwind a lot lately on comiCSS 😳
At this point it feels like the Church of Tailwind gaslights people. It breaks many clean code basics like avoid mental mapping, yet we are told that this approach is cleaner and more efficient than writing normal CSS. It's for people who don't get that locally styling everything from zero is the polar-opposite of the design of CSS. Probably it's the same batch of people who tries to go full-OOP or full-FP in JS not understanding that, sadly, the design of the language will always break important details of either approaches.
Sometimes I feel like Tailwind advocates live in a weird fantasy world. So much stuff they say just doesn't seem to conform to reality, like when they say you need to know CSS to use tailwind correctly, or that it makes code cleaner, etc.
I think the main allure is maintainability and code confidence. If you're code isn't dependent on custom "named" classes then you never have to worry about breaking something somewhere else when making a style change. How many times have you changed a class style only to realize it breaks some implementation somewhere else in your app that you now need yet another custom class for though? To your point, no it doesn't make style declaration cleaner, it makes it so you don't have CSS files 1000's of lines long with 100's of unique classes defined that have maybe 1 or 2 property differences.
I'm not a Tailwind advocate but there are legitimate use cases where the philosophy behind Tailwind makes sense. For instance when an app gets too large to maintain any reasonable sense of where classes are applied and you're able to confidently say, "making this style change will only effect this scenario". Or, you have multiple people working on separate teams changing code on the same app. Is Tailwind pointless on a marketing website? Probably. Does it make your mark-up more complex and harder to read? Yes. When you're dealing with an application with 100's of features and UI components and multiple teams though... you'll trade the time it takes to read Tailwind for not having to account for class duplication or test, and fix, your changes to an existing class breaking a different implementation in the app.
Saying that something is more maintainable and at the same time more complex and difficult to read (later in the comment) is contradictory. Complexity and difficulty to read make the code more difficult to maintain. What is it?
Almost none. To be honest, I can't remember having that problem at all. Following a methodology similar to BEM (not necessarily BEM) will avoid that problem completely. If your class is something like module-component-element, you will not get name conflicts and it will be easy to know what each class represents (both in HTML and CSS).
The CSS code generated by tailwind is literally CSS files with 1000s of lines of code with unique classes with just one property. You may not see how the sausage gets made, but it gets made anyway.
Don't take me wrong. Tailwind has good things: CSS code pruning which is great, the apply directive (discouraged by the authors), cross browser support (it adds vendor prefixes)... But I wouldn't list maintainability or small code as pros. I would consider them neutral or put the in the cons column.
what's meaning?
Array.sort sorts as string, so 100 will be before 20. You need a compare function to fix that.
LOL, I forget about that.
H: Yes
I: Don't call me, send an email.
I saw these on X (formerly known as Twitter) and Reddit recently…
haha it's the same with frontend developer and UI / UX Designer 😂
I am an artist trying to learn coding, so I can build games
If you don't get it, it's funny because JS arrays begin at 0.
any language's arrays begin at 1?
Lua.
aha, that is really fun
Lua "arrays"* begin at 1
* Lua doesn't really have "arrays", but sequences are functionally the same thing, and those start at 1
Lua
Or as happened 3 weeks ago, client cancelled project after 4 months in prod, when it took 7 months to design and build! Oh well, I guess I still got paid.
I just LOVE this one! 😁
🐍
Win+Vwill save youIt stands for "Grenade Launcher" because you're going to want one
I took up photography, it's creative, I get outdoors and I get to control how much or how little I use tech. I shoot film on landscapes, almost none. I shoot digital on architecture and I use loads, to the point I was writing Golang utils to get image meta data extracted
Hahahahah! 🤣
so accurate