Future CSS
J. Ky Marsh

Can you share a bit more about your motivation, and what you’re trying to accomplish? Some of what you describe squarely confronts proven best practices, and perhaps you could provide showcases or other tangible evidence how this neglect of best practices would not only fall on people’s feet, but crush them? (I love drama.)

As I have suggested in two light comments, principles like Separation of Concerns—which is behind the idea of avoiding presentational markup—and Don’t Repeat Yourself are key to maintainability; other areas of concern like performance, but also code understanding, don’t seem to be covered. Maybe some extra notes and links can strengthen your points.

(Otherwise I’d respond with the vision that we’ve usually benefited from, one that, in complex projects, leads to following one development approach in particular, tailoring.)

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.