To me, it is the difference between being an amateur "blogger" and a professional Writer/Columnist/Reporter.
I get the feeling that you know versioning is a good feature to have, but you are looking for an excuse not to have to change your design :-)
The more professional the publisher, the more important it is to have versioning. Why: if someone fixes a typo by accidently removing an entire paragraph (and that happens to pro's too) the last thing you want is for the editor to have to go into his own archives to find the paragraph and paste it back in. If the editor is not near his workstation it can take hours before he can fix the articlel which is not acceptable.
And if you're publishing legal documents it is a simple requirement that older versions must be available, it's not even debatable.
But like I said, it's perhaps more a matter of how complex the solution is. Creating a backup version requires only one trigger and a table and you will get an automatic version for every change in a record, no extra work on your part at all.
And I can't imagine that calling up an older version in your application is very difficult.