&gt; It could have been fixed 15 years ago. And when it appeared it broke a ton of librairies developped during those years, like CSS grids and stuffs like jQueryUI which still has some incompatibilites.<p>And a hundred different problems with C could have been fixed any number of times, and that doesn&#x27;t make it a bad tool.<p>&gt; Getting there? After 15+ years?<p>I&#x27;m sorry, would you prefer it took 30? Is it not better that progress happens than not? The CSSWG is a glacial apparatus that create some of the worst bureaucratic bullshit I&#x27;ve ever seen, but CSS itself isn&#x27;t a bad tool. Thanks to browser makers adding proprietary extensions they all agree on then shoving it down the throat of the WG helps a lot.<p>The pace of progress still doesn&#x27;t mean it&#x27;s a bad tool, or worse than what we had.<p>&gt; Just try something basic : animate an element along a sinusoidal path in CSS. Look at the code you get .
&gt; Then try the same in JS.<p>Still doesn&#x27;t prove CSS is somehow the worst thing ever and kill puppies.<p>Yes, programming for the web is hard. Programming is pretty much always hard, no matter how easy we make it because humans suck at long term planning. CSS is still leaps and bounds better than what we had, and makes a lot of things incredibly easy.