4 ms·
Yeah this could quickly devolve into a flame about divs vs tables. But divs I always saw as a step backwards in one aspect: programmer ease of use. In divs yo
by barmstrong 16y ago
Yeah this could quickly devolve into a flame about divs vs tables. But divs I always saw as a step backwards in one aspect: programmer ease of use. In divs you have to spend time thinking about "float drop", doing math in your head, and getting all the columns to have the same height - things which "just work" in tables. It still surprises me sometimes how quickly they were adopted.
- petercooper 16y agoBut divs I always saw as a step backwards in one aspect: programmer ease of use. It's always a lot easier at first to overlook structure in your app/code/whatever. It's when you or others come to work with your code or extend it in some way (with Greasemonkey, say) that all the extra work comes along. If you have to "spend time thinking about" writing tests, it takes longer to build the prototype of your software but.. that's not a particularly good rationale for not using tests (though it is still a rationale, of course). Same goes for semantic markup in my book.