I’m sorry I also seems to miss your point. Care to elaborate?
Inderpal Singh
1

Hi Inderpal. My point is that this is a very poor way of doing CSS. It doesn’t scale, is not maintainable, it drops the power of doing CSS andit mixes the structure of the document with the styling of the document in an unhealthy way.

It betrays a poor understanding of CSS, and is a “solution” that someone might come up with if they thought CSS was broken and difficult — that stereotype back-end developers seem proud to believe. A front-end developer tasked with changing styling or implementing designs in software that used this methodology would be frustrated, and have to fight against the foolish limitations. Their work would be slow and the output continually unmaintainable. I include all the associated links and writings in this too.

Put yourself in your back-end developer shoes and look at something like “Simple Python” which I just made up: No loops, because they’re confusing. Functions jump around a lot and nobody uses them anyway so we ditch those. If you need to do anything more than once just copy-and-paste it below, everybody knows how to copy and paste! You’d think the person who made that at worst hadn’t learned to program and at best did not respect what they could achieve with the fundamental concepts.

TL;DR It throws away the good bits of CSS and exchanges it for bad ones.

Show your support

Clapping shows how much you appreciated Gavin van Lelyveld’s story.