Re:CSS: It was twenty years ago today
by agumonkey on Friday October 10, 2014 @06:35AM
(#8437054)
Interesting, since table based layout gave such ugly html sources. CSS might be incomplete, and too programmer oriented, but it has some value (it abstracts halfway).
[ Parent
| on HN ]
<div class="container">
<div class="row">
<div class="col-xs-4">
What do you mean tables produced ugly html?
</div>
<div class="col-xs-3">
Looks totes modern to me ...
</div>
</div>
</div> <body>
<main>
<p>It can be much better if you avoid abusing
HTML classes for style.</p>
<p>Classes are meant to describe the role of
the tag, not its presentation.</p>
</main>
<aside>(use Sass instead)</aside>
</body>
-- /* Sass + Neat */
body { @include outer-container; }
main { @include span-columns(4); }
aside { @include span-columns(3); }Unfortunately in the reason world you tend to design components that can be used anywhere in the page (and hopefully reused in different pages) so you don't get the freedom to work this way.
Unfortunately true, although the Shadow DOM could help fix that.
I agree. We were producing the cleanest HTML back when "semantic web" was all the rage. Around 2009 I guess?
Are you kidding? The semantic web was just a bunch of extra junk layers of indirection. Schematize everything, but nothing's actually using the schemata. Replace your <i> tags with <em> tags, because that's more semantic, and easier for a screenreader to interpret (this was a real argument made at the time). Write your actual page as an XSLT on top of what we'd now call your API - but XSLT is barely human-writable, never mind human-readable.
Before looks were everything and HTML reduced to a presentational markup?
I miss them days.
Maybe I was conflating two things, deeply nested tables AND inline style (norm of that era).
Ah yes, we've at least gotten over the inline css ... although we seem to have gotten back into inline javascript with various ng-click="doSomething()" thingies.
Sadly yes, and worse, people seem to enjoy this way. sigh
A good talk about that is "Pete Hunt: React: Rethinking best practices -- JSConf EU 2013" http://www.youtube.com/watch?v=x7cQ3mrcKaY
When you do everything from inside JS (as Pete advocates) then you have a real programming language to work with. Inline JS in the HTML is much less expressive.
As I wrote a few weeks ago[1], I hate this way but I can't argue with results. It's quicker and simpler to solve low-hanging fruit this way, which lets me spend cycles on application logic.
[1] http://swizec.com/blog/i-was-wrong-about-angularjs/swizec/66...