After exploring why frameworks and why not frameworks, I dive into the design priorities I think a web framework should have.
We explore three arguments against frameworks, address them, then turn them into challenges to be overcome.
While contemplating a Clojure web framework, I explore the reasons we use web frameworks in general. I conclude that the framework should support a learnable development process.
One of the great things about very robust and powerful abstractions is that they can give you tremendous leverage. The leverage can be so great that you can build something much greater than the sum of its parts. However, I worry that the web is an end to this kind of abstraction. I’d like to explore why that is and what we can do about it.
One reason to separate style from content is to reuse HTML or CSS. Ultimately, we would like a solution where we can reuse both.
Reference: Healthcare.gov and the Gulf Between Planning and Reality Clay Shirky nails it with nice, narrative style.
LESS and Sass (and similar solutions) have saved CSS for three reasons: separation, abstraction, and cascading. While I welcome them, CSS still has other problems which I believe can be solved.