4 ms·
It wasn’t an opinion, but I think you gave me the answer anyway, which seems to be “students learning CSS”. I never learned CSS like this, so I wouldn't think o
by soneca 3y ago
It wasn’t an opinion, but I think you gave me the answer anyway, which seems to be “students learning CSS”. I never learned CSS like this, so I wouldn't think of it.
I started learning CSS only about 6 years ago. So I had Stack Overflow and MDN web docs for it.
- timr 3y agoThe answer, as with all code, is "you, six months from now". Anything that makes your code less readable is a fail. I understand that people want to treat CSS and HTML as assembly, but that's a leaky metaphor, and only works insofar as you never have to debug an actual webpage. Every place I've ever seen with tailwind has struggled with front end work, because the end result is so horribly abstracted from the code.
- soneca 3y agoThat code posted above is the compiled code in the browser. The developing code is not unreadable like that one. I think Tailwind is very readable during development. Even if I had only used in side projects.
- paulryanrogers 3y agoThe meaning of 'compiled' has shifted quite a bit. We used to say transpiled when the output wasn't byte or machine code.
- timr 3y agoYes, I know. Tailwind emits this kind of gibberish as a compilation step, which makes it much harder to figure out what's breaking when you're using a browser inspector or something. Which of the 83 different classes is the problem? Good luck! You have to have a certain level of discipline to write clean CSS, but it really isn't that hard. It shouldn't take a 300-character inline style to make a button, when you can use CSS as intended, and have a class named "button".