Re:“Tomato” versus “#FF6347” – the tragicomic history of CSS...
by antod on Thursday October 15, 2015 @06:57PM
(#10396519)
No thanks.
FONT is listed as "obsolete, non conforming, not to be used" in the HTML5 spec.
It couldn't do very much in terms of styling anyway.
I would rather keep styles in a reusable cachable resource than bloat out the HTML.
I would rather styling changes NOT turn into coding exercises, especially ones that cause a massive 'WTF?' for some future maintainer.
Re:“Tomato” versus “#FF6347” – the tragicomic history of CSS...
by olavk on Friday October 16, 2015 @08:28AM
(#10398802)
Seriously, you think programatically transforming a document into presentational html is simpler than using a css selector?
Re:“Tomato” versus “#FF6347” – the tragicomic history of CSS...
by lmm on Friday October 16, 2015 @02:58PM
(#10401356)
I already build up my HTML programmatically from reusable components, following DRY (Don't you?). That means the markup for what it means to be e.g. a paragraph heading is already in one place. It's no trouble to style it there, with a font tag, and if I want to change it then I can change it there. And if I want to abstract out a particular piece of styling and reuse it across several components, it's just code, I factor it out the same way I would anything else.
So yes, seriously, it's simpler than using a CSS selector.
Re:“Tomato” versus “#FF6347” – the tragicomic history of CSS...
by rubbingalcohol on Thursday October 15, 2015 @06:00PM
(#10396296)
What if you don't want to use a CMS?
Have you tried using FONT recently? (Or indeed, any time this decade?) When you're generating your pages programmatically it's really easy to separate content and presentation concerns in code but then combine them when finally rendering the page. You can use a normal programming language which is much clearer than CSS selectors. CSS was necessary in the days of hand-written HTML, but once you have a CMS you might as well use FONT and inline styles (possibly using CSS just with single classes, as a kind of "cache" to avoid repeating the same inline styling block everywhere).