In message said:
Yeah, I was also playing around with some other stuff at the time (which
is why .author is a block level item), but the columns work on all
the browsers I use, so that is good enough at least until they go with
the standard column-count directive.
I've had to do a lot of these dual column things over the ages, and it's
nice to know I can put aside all those hacks and floats and can
trivially change from 1 to 2 to 3 to 6 columns.ZZ
Using css3 is absolutely fine for personal use, simply because
you know the browsers that support it.
It is also fine for public use when you don't know what browsers
will be used if you make the pages have a fallback look that you
deem satisfactory (and one that is beyond mere el basic browser
defaults). Sort of 'do no harm'!
In the example you gave, the main thing that many would not like
even if they were using supportive browsers was the lack of
fluidity. I think quite a few of us would need to be horizontally
scrolling a fair bit or else ensure our browsers were about
1400px or near there (way too wide out of *necessity*).
Just by the way, considering your example of book titles and
authors, my first thought would be to markup with a two or three
col table. But that might not have suited your needs. It would
certainly suit the ordering, and be html semantically richer.