#csslayers — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #csslayers, aggregated by home.social.
-
Next.js has two critical bugs that make it troublesome when developing in a non-Tailwind project.
I recently encountered them and spent much time trying to make my project work again, but failed.
When I browsed the issues, I found that I was not alone.
#79531: https://github.com/vercel/next.js/issues/79531
#83941: https://github.com/vercel/next.js/issues/83941#vercel #nextjs #tailwindcss #webpack #turbopack #css #csslayers
-
Next.js has two critical bugs that make it troublesome when developing in a non-Tailwind project.
I recently encountered them and spent much time trying to make my project work again, but failed.
When I browsed the issues, I found that I was not alone.
#79531: https://github.com/vercel/next.js/issues/79531
#83941: https://github.com/vercel/next.js/issues/83941#vercel #nextjs #tailwindcss #webpack #turbopack #css #csslayers
-
Re: Affordances and Lean CSS
Stephen Margheim (fractaledmind) wrote Affordances: The Missing Layer in Frontend Architecture this month. This quick post is my reply to his great article. I hear the objection already: “Isn’t this just… semantic CSS classes? We tried that.” You’re right that we tried it. But “it didn’t work” deserves unpacking. I was indeed objecting that in my mind. But I was not thinking, "it didn't work." I was thinking, "and it has kept working for decades. Obviously the utility-only workflow described is terrible; it's why I refuse to choose Tailwind. How are affordances better than what's worked for a decade?" […]https://kerrick.blog/posts/2025/re-affordances-and-lean-css/
-
Re: Affordances and Lean CSS
Stephen Margheim (fractaledmind) wrote Affordances: The Missing Layer in Frontend Architecture this month. This quick post is my reply to his great article. I hear the objection already: “Isn’t this just… semantic CSS classes? We tried that.” You’re right that we tried it. But “it didn’t work” deserves unpacking. I was indeed objecting that in my mind. But I was not thinking, "it didn't work." I was thinking, "and it has kept working for decades. Obviously the utility-only workflow described is terrible; it's why I refuse to choose Tailwind. How are affordances better than what's worked for a decade?" […]https://kerrick.blog/posts/2025/re-affordances-and-lean-css/
-
Re: Affordances and Lean CSS
Stephen Margheim (fractaledmind) wrote Affordances: The Missing Layer in Frontend Architecture this month. This quick post is my reply to his great article. I hear the objection already: “Isn’t this just… semantic CSS classes? We tried that.” You’re right that we tried it. But “it didn’t work” deserves unpacking. I was indeed objecting that in my mind. But I was not thinking, "it didn't work." I was thinking, "and it has kept working for decades. Obviously the utility-only workflow described is terrible; it's why I refuse to choose Tailwind. How are affordances better than what's worked for a decade?" […]https://kerrick.blog/posts/2025/re-affordances-and-lean-css/
-
Re: Affordances and Lean CSS
Stephen Margheim (fractaledmind) wrote Affordances: The Missing Layer in Frontend Architecture this month. This quick post is my reply to his great article. I hear the objection already: “Isn’t this just… semantic CSS classes? We tried that.” You’re right that we tried it. But “it didn’t work” deserves unpacking. I was indeed objecting that in my mind. But I was not thinking, "it didn't work." I was thinking, "and it has kept working for decades. Obviously the utility-only workflow described is terrible; it's why I refuse to choose Tailwind. How are affordances better than what's worked for a decade?" […]https://kerrick.blog/posts/2025/re-affordances-and-lean-css/