It makes a lot of sense to programstically generate css because all of what the author said is true: global namespace, difficulty to trace specificity, modularity, etc. I am not convinced inline styles are the way forward. You can just as easily write (manually or programmatically)your styles using css&#x2F;sass&#x2F;less and optimize and serve them.<p>You can just do it server side. You can create global classes for objects and elements and include the
 However you want. You can optimize on your own server FOR THE CLIENT, and serve the best result.<p>It is dogmatic, but I don&#x27;t like inline styling. I think it should really be limited to values that are expected to regularly fluctuate during a session. This would be your height or width resizing on an animation or something where the x or y moves. These usecases make sense because you directly apply animation to an element.<p>Can you imagine what the dom would look like with html, javascript, css, sass, markdown and haml&#x2F;ruby all on a page? I hope there is a way to demonstrate your page to Search Engines, because eventualu they may stop believing the alternate robots files if they just cant tell what is going on. Also, writing your own tags and attributes, I like it think it&#x27;s helpful, but DOMs don&#x27;t make sense anymore.