8 ms·
<div class="container"> <div class="row"> <div class="col-xs-4"> What do you mean tables produced ugly html? </div>
by Swizec 12y ago
<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>
- agumonkey 12y agoMaybe I was conflating two things, deeply nested tables AND inline style (norm of that era).
- Swizec 12y agoAh 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.
- agumonkey 12y agoSadly yes, and worse, people seem to enjoy this way. sigh
- Swizec 12y agoAs 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/6602 http://swizec.com/blog/i-was-wrong-about-angularjs/swizec/66...
- DougBTX 12y agoA good talk about that is "Pete Hunt: React: Rethinking best practices -- JSConf EU 2013" http://www.youtube.com/watch?v=x7cQ3mrcKaY http://www.youtube.com/watch?v=x7cQ3mrcKaY
- ufo 12y agoWhen 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.
- deleted 12y ago[deleted]
- gioele 12y ago<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); }
- Swizec 12y agoI agree. We were producing the cleanest HTML back when "semantic web" was all the rage. Around 2009 I guess?
- porker 12y agoBefore looks were everything and HTML reduced to a presentational markup? I miss them days.
- lmm 12y agoAre 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.
- Touche 12y agoUnfortunately 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.
- blowski 12y agoUnfortunately true, although the Shadow DOM could help fix that.