Tailwind should be considered a legacy tool at this point. Use the CSS language as it was designed instead of inventing another markup-based styling language, which leads to basic software anti-patterns (e.g. magic numbers or abbreviations like "pt-0.5"), a maintenance nightmare, and a huge knowledge gab. #webdev #reactjs #css #softwareengineering #tailwindcss
It's just a tool, you can stop using it
Completely agree with this. Modern CSS has evolved to the point where a framework simply isn’t needed - unless you don’t understand CSS…
Tailwind should be considered a legacy tool at this point. Use the CSS language as it was designed instead of inventing another markup-based styling language, which leads to basic software anti-patterns (e.g. magic numbers or abbreviations like "pt-0.5"), a maintenance nightmare, and a huge knowledge gab. #webdev #reactjs #css #softwareengineering #tailwindcss
Couldn't agree more on this take on Tailwind. I’m a firm believer in separation of concerns, and I still prefer keeping my SCSS separate. Even when scaffolding new projects with AI, I find it constantly gravitates toward Tailwind. I often find myself questioning if I’m just being a 'grumpy old man' as I refactor it back to SCSS, but there is something to be said for the maintainability and clarity of a dedicated style sheet.
Tailwind should be considered a legacy tool at this point. Use the CSS language as it was designed instead of inventing another markup-based styling language, which leads to basic software anti-patterns (e.g. magic numbers or abbreviations like "pt-0.5"), a maintenance nightmare, and a huge knowledge gab. #webdev #reactjs #css #softwareengineering #tailwindcss
Agree 1000x 👍 I don’t understand how anyone thought Tailwind was a good idea in the first place. I imagine its support coming from a wave of secret-CSS-haters who didn’t understand CSS’ inherent beauty 🤷🏻♂️
Tailwind should be considered a legacy tool at this point. Use the CSS language as it was designed instead of inventing another markup-based styling language, which leads to basic software anti-patterns (e.g. magic numbers or abbreviations like "pt-0.5"), a maintenance nightmare, and a huge knowledge gab. #webdev #reactjs #css #softwareengineering #tailwindcss
https://pretextjs.dev A new frontend library called Pretext (March 2026) is trying to change how we handle text layout. Current approach: Render → Measure → Re-render Pretext approach: Calculate → Render once Instead of using DOM measurements like getBoundingClientRect(), it lets you: • Predict text size before rendering • Avoid layout shifts • Reduce re-renders Useful for: • Chat/message UIs • Infinite scroll lists • Dynamic cards • Multilingual layouts It works without the DOM and can run on the server as well. Still new, but interesting direction for performance-focused UIs. #frontend #javascript #reactjs #webperformance
Did you know that we can leverage the #frontend tech stack to generate videos? That's the promise of Remotion! In this simple Stackblitz project (https://lnkd.in/e8AGkNhs), we can see how to create a video by using #HTML, #JavaScript, and #CSS. In detail, Remotion renders the React component frame-by-frame in a headless browser, driven by a frame counter. #ffmpeg then encodes the sequence of frames into an MP4. To generate the video: `npx remotion render SourceAnimatedComponent out/video.mp4` And here is the output!
For years, CSS developers dreamt of a 'parent selector.' Well, it's here! The `:has()` pseudo-class lets you select an element based on the presence, absence, or state of its descendants. Most devs still struggle with complex JavaScript or convoluted class toggles to achieve what `:has()` does natively. This often leads to brittle code, layout shifts, and unnecessary performance overhead. Imagine styling a form element only if it contains an invalid input, or highlighting a navigation item if its submenu is open, all without a single line of JS. Ignoring `:has()` means missing out on cleaner, more performant, and purely declarative CSS. Are you still writing it the old way? #css #cssTips #frontend #webdev #developers
I’ve seen senior developers get tripped up by this. CSS Specificity. One of those concepts you ‘know’… until it bites you in production. Here’s the thing most developers learn CSS by copying and pasting. Or directly using with libraries like Tailwind and Bootstrap. So when styles stop working, the reflex is: → Add !important → Add an ID → Give up and use inline styles And then the codebase turns into a specificity war nobody wins. Here’s what actually matters: → Inline styles beat everything (except !important) → IDs (0,1,0,0) beat classes (0,0,1,0) every time → !important isn’t a selector it overrides the cascade entirely → The more specific your selector chain, the harder your CSS is to maintain The real skill isn’t memorizing the hierarchy. It’s structuring your CSS so you rarely need to fight it. Design systems, BEM, utility-first (Tailwind) — they exist largely to prevent specificity wars at scale. See the quiz in the image 👇 Drop your answer in the comments easier than you think! #CSS #Frontend #WebDevelopment #React #JavaScript #UIEngineering
Struggling with CSS layouts? 🤯 Flexbox is the tool that changes everything — and once it clicks, you'll never go back to float hacks again. I just published a full breakdown of CSS Flexbox on hamidrazadev.com — from the basics to the most common mistakes developers make. Whether you're just starting out or need a solid refresher, this one's for you. 💡 Check it out 👉 hamidrazadev.com #css #flexbox #webdevelopment #frontend #learntocode #csslayout #developers #100daysofcode #websitedesign #codingtips
Yeah, I know — Tailwind CSS v4 came out in January 2025. I'm late. But after using it on real projects, I had to write about it. Because this isn't just a faster v3. It's a fundamentally different way of thinking about CSS tooling: → No more tailwind.config.js — everything lives in CSS → Lightning CSS engine — incremental builds 100× faster → Dynamic utilities — just write grid-cols-15, no config needed → Container queries in core — finally → OKLCH colors — more vibrant, more accurate I wrote a full breakdown on my portfolio. Link in the comments 👇 #TailwindCSS #Frontend #CSS #Vue #WebDevelopment
🚀 Website Performance Series – Part 5 Many developers focus only on images… but ignore JavaScript impact. Heavy or blocking JS can: • Delay interaction • Increase load time • Hurt user experience ✔ Always audit scripts: • Remove unused • Defer non-critical • Limit third-party usage #JavaScript #Frontend
I understand (and agree) with your perspective. Tbh tailwind got the hype because of shadcn and AI. Other than that, tailwind has been there but the industry was dominated by MUI and its styled components. Tailwind is pretty unreadable at times. There are 8 9 lines of stringified classnames, by the time we reach line 2, we forget what was on line 1. No one imo actually reads any of those class names. It SOUNDS cool that people can type faster, but honestly I didn't like it. MUI's sx prop was the beast. Now with AI doing most of our stuff, tailwind seems like a go to plan. I just ask AI to change my shadow XD