News for hackers. Stuff that matters.
Re:Tailwind CSS v3.3 by swyx on Wednesday March 29, 2023 @09:41AM (#35357153)
i think you're kinda proving his point. it's easy to write "BAD CSS". I write "BAD CSS". you may be so good you only write GOOD CSS. i'm not. I may never be as good as you. tailwind is a framework for people like me. (there are lots like me)
Re:Tailwind CSS v3.3 by emmacharp on Wednesday March 29, 2023 @09:59AM (#35357379)
CSS is really not that hard to understand and use adequately. And as I said here, linting should be more than enough to nudge you in the right direction, CSS-wise.

Or maybe you don't like CSS at all?

Re:Tailwind CSS v3.3 by pcthrowaway on Wednesday March 29, 2023 @12:01PM (#35359151)
Are you managing the entire front-end stack? Or just design?
Re:Tailwind CSS v3.3 by emmacharp on Wednesday March 29, 2023 @03:50PM (#35362391)
It depends on the project. More HTML and CSS than JS. But, as I said, the team has been generally using the Tailwind paradigm for 5 years now. The team has also been divided for while about it. Heheh.
Re:Tailwind CSS v3.3 by mhoad on Wednesday March 29, 2023 @02:20PM (#35361142)
I also used to feel like the comment you were replying to. About two years ago I decided to try and lean in heavily towards “modern” CSS and honestly things have gotten so much better the past few years.

I also leaned in heavily to the component model with Web Components which was another huge win for my experience with CSS.

I actively enjoy it now rather than dread it. Catching up wasn’t too difficult and if someone else is in the same boat I would recommend the investment.

Re:Tailwind CSS v3.3 by emmacharp on Wednesday March 29, 2023 @03:51PM (#35362405)
My thoughts exactly!
Re:Tailwind CSS v3.3 by Xeoncross on Wednesday March 29, 2023 @09:57AM (#35357353)
If Shawn can't write good CSS, I'm hopeless