News for hackers. Stuff that matters.
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by namuol on Sunday February 15, 2026 @11:27PM (#47030886)
Obfuscate? I can learn tailwind and use it in dozens of projects. I can use tailwind in my project and onboard dozens of developers immediately. I can learn your CSS conventions and use them in exactly one project.
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by nilslindemann on Monday February 16, 2026 @12:06AM (#47031103)
Why can you use CSS conventions in only one project?
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by manuelmoreale on Monday February 16, 2026 @02:07AM (#47031813)
He wrote "learn your CSS conventions" which implies that every team and every project will have a different set of conventions. Hidden inside that statement is the fact that he just accepted that Tailwind should be THE CSS convention, something I personally disagree with but to each their own.
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by namuol on Tuesday February 17, 2026 @01:57AM (#47044489)
No. Tailwind is a way of writing css, not a convention. By “your” convention I’m referring to the problems with the cascade, ie naming classes and so on. I’m not saying tailwind is the only other way. There are many ways to write CSS but doing it with something bespoke for your situation is usually a bad idea.
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by UqWBcuFx6NV4r on Monday February 16, 2026 @05:12AM (#47033214)
Can we all just drop words out of comments that we reply to if it makes it easier to make our point?
Re:Modern CSS Code Snippets: Stop writing CSS like it's 2015 by namuol on Tuesday February 17, 2026 @01:58AM (#47044492)
You can try to rely on conventions across projects, sure. It doesn’t work well.