Re:Separation, Abstraction, and Cascading in CSS
by angersock on Saturday December 29, 2012 @02:13PM
(#4983051)
More like, without them you will likely reinvent (badly) some subset of HTML+CSS+JavaScript.
The problem is that you want to organize the content of the document (HTML+DOM) with annotations and whatnot, and then style it to look pretty or position it just-so (CSS), and then finally maybe add some goofy runtime logic or updating (Javascript).
We've got tools that have evolved already to solve these three problems, so why not use them? One of the happiest days in my life was getting to do UI development on the web instead of an AWT/SWT/Swing behemoth (CAD software in Java) or really clean but subgreat visualization/menu framework (C with OpenGL, C++ with rendering interface, various other toolkits over time).
Re:Separation, Abstraction, and Cascading in CSS
by mcartyem on Sunday December 30, 2012 @03:02AM
(#4985052)
why not use them?
Because they are not powerful enough.
Re:Separation, Abstraction, and Cascading in CSS
by saraid216 on Saturday December 29, 2012 @03:25PM
(#4983307)
> An alternative would be to use a more powerful language
...can you show us an alternative?
An alternative would be to use a more powerful language that would let you express the kinds of things you often need with CSS as macros and have no CSS at all.