[donerKebab]

It's not because it's old.

It's because it's semantically incorrect.

It's because positioning is done in the html. It is generally considered a good thing to separate areas of concern. Content in one place, style in another.

[Johngibb]

I think the question is _why_ is it important to be semantically correct, not do positioning in the html, and to separate areas of concern. Note - I agree with you, I'm just clarifying the question.

I think the answer is really only two things:

1) Accessibility. A screen reader can probably work better with semantically valid markup. I've not much experience with these, but it's my assumption.

2) Ease of development when making changes. This one is purely for the developer, not the end user. It's probably true, but there are definitely cases where just throwing a table at the problem is simpler than CSS, especially for someone not up on HTML5.

What else?