Meme Monday!
Today's cover image comes from last week's thread.
DEV is an inclusive space! Humor in poor taste will be downvoted by mods.
Reminder: Every day is Meme Monday on DUMB DEV β¨
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (100)
EPIC lol
Very creative and true. Debugging is all in one.
Haha I just saw a similar one at a pub quiz yesterday -
caption was "Moving our data center to the cloud"
AI's take on today's cover image joke
Today's comiCSS cartoon:
Why does everyone mock tailwind? It's a great toolset.
Short answer (for this particular case): this is a comic about CSS, poking fun at Tailwind is almost a given. But it's all in good fun.
But why? It's a very great toolset for large projects.
It is a little bit of many things. From a technical perspective, Tailwind has shortcomings (just like any other tool): steep learning curve, bloated HTML, readability and maintainability challenges, poor separation of concerns... But some of the reasons are not necessarily technical: its creators use some aggressive marketing and its community includes many obnoxious supporters who fail to see the tool's shortcomings and will defend Tailwind as the panacea for web styling, when it isn't. It's just a tool, like many others. Used correctly, it will be great; used poorly, it will be terrible... Just like any other tool.
Yea... I probably fall into that "use poorly" group by using it with clsx and scss.
"Large projects" are probably the least fitting targets for Tailwind, where a possibly large variety of developers with different levels of experience will have to deal with that arbitrary layer language over CSS, intricate styling mechanisms are expressed in unstructured lists of strings, automated RUM reports are rendered incomprehensible ("83.2% of users clicked on [.list.of-36.css.'classes']"), most of Tailwind's alleged advantages don't matter and names and semantics are most important.
Tailwind makes us sloppy coders.
The goal behind Tailwind is almost exactly the opposite of the goal of CSS. It wants to combine style and content, so to make a change you need to edit all of your components individually. Its examples and "best-practice" rely on nesting a lot of junk elements, which ties into the stated aim of killing separation, and the solutions to the problems it introduces are effected with multiple additional build steps to get to the point where it's nearly as useful as CSS was in the first place.
Tailwind is for those who don't understand CSS/SASS.
I mainly use tailwind for styling, and I use scss (sass, but with css syntax) for complex styles that tailwind does not have classes for
I mainly use tailwind for layout and responsivity. I don't spend my time to style.
It's really reverting notion of styles being separate from template (which is a good thing). It pollutes the markup and that's it. Modern CSS is so powerful and easier than before at the same time, that you don't really need any additional thing on top of it.
I would recommend the "tailwind fold" extension for vscode, but it doesn't play nice w/ clsx
Or I can just keep not using Tailwind :)
Why is this actually accurate though? π€£ππ€£
Aw, I love the kawaii one :3
Remember those vids where the monitor goes flying out the windows?
Yup this is it!
Certainly raises blood pressure and I have low blood pressure.
there, there...
Hahah xD
happened to me actually xd
hahaha!
this gave me a good chuckle XD
Stack Overflow answers are always Microhard.
This is the reason for the recent layoffs at Microsoft.
Now do ChatGPT.
so real
this is reality
Some comments may only be visible to logged-in visitors. Sign in to view all comments.