Why developers should replace JavaScript with modern HTML and CSS alternatives
A collection of bad practices in HTML, copied from real websites.
Read the full articleYou might also wanna read
Why an HTML-first approach outperformed heavy SPA frameworks for our website
Starting a few years ago, I realized some junior and medior engineers never once considered the possibility of building a website (app, expe
news.ycombinator.com·1mo ago
CSS vs. JavaScript Animations: A Nuanced Performance Comparison
There are a bunch of JavaScript animation libraries out there, and you might have wondered whether there’s a performance cost compared to tr
joshwcomeau.com·1mo ago
Modern CSS Techniques for Creating Memorable Web Experiences
There are many ways to create memorable experiences. Sometimes it's as simple as a form that completes smoothly. But here I'm interested in
CSS-Tricks·1mo ago
State.js: A CSS-Reactive Framework That Replaces JavaScript Logic with CSS Variables for UI State Management
State.js is a CSS‑reactive framework that makes UI state and updates flow through CSS instead of JavaScript logic. - iDev-Games/State-JS
github.com·1mo ago
Rethinking Mobile-First CSS: When the Classic Approach Falls Short
Is mobile-first CSS always the best option? Patrick Clancey explores the pros and cons of the classic methodology, as well as when other sol
A List Apart·4y agoJavaScript Fatigue in 2026: How to Cope With Framework Churn
Stop chasing every new JS framework; focus on web fundamentals, pick a default stack, and time-box experiments to avoid churn.
Comments
Sign in to join the conversation.
No comments yet. Be the first.