>And despite your crude last jibe at web developers attracted to Tailwind's model, No my jibe was at web developers in general. CSS and HTML are quite simple r

>And despite your crude last jibe at web developers attracted to Tailwind's model, No my jibe was at web developers in general. CSS and HTML are quite simple really. If you actually keep things semantic and build your document properly with appropriate markup ... lo and behold things just work properly. I can understand the divistush of the past when CSS 1 and 2 were quite limited. However today there is simply no excuse. > most competent web developers will be able to quite easily pickup this very sane CSS utility framework :) Sure I can read it. The problem is with things like this is that you are learning how to work with their model that basically doesn't work like CSS is supposed to work. So you it essentially nullifies your existing skillset and forces you into using their framework. I bothered to actually learn CSS properly and understand the technology and then I have to work with something which basically throws that all out the window and forces me to work how they want me to build stuff. No thanks. If you think that is a "sane" way of working, I really don't know what to say.