I think Tailwind appeals to « back of the front end » devs which is a role that didn’t exist until 2010 or so? I think tailwind is valuable and as always midd

I think Tailwind appeals to « back of the front end » devs which is a role that didn’t exist until 2010 or so? I think tailwind is valuable and as always middle way is the best approach but more difficult to structure and definitely not good for commercial purposes. My favourite way is to put tw classes for spacing components and layout directly in the template while using bem-like naming for the component ‘s own appearance. Having utilities like mb-2 that can override the default set in a component I think solves many headaches and is one of the strengths of having a full set of utilities. However I also find a real strength is having a standard accross devs AND projects and so when tailwind advises to customise your project. Change the meaning of mb-4 or text-lg then I find it completely undermines the value of having a standard utility set.