Doing a "hard fork" is hard, but maybe better than putting in some automatic adjustment that someone could end up "gaming".
If each time the limit is to be raised another megabyte, or each time it is to be doubled, the whole "hard fork" thing has to be gone through again that might provide some security at least until the developers get the hard fork techniques down to a point where it becomes pretty much just a "rubber stamp" that goes along with whatever change they decide to make next.
Clearly blocks are plenty big enough currently, maybe even too big, since we are clearly not losing per bitcoin price/value due to high transaction fees nor are we even managing to discourage "frivolous" transactions (like "sorry, you lost, please try again" type messages which probably belong in IM or some other kind of chat system not in the world's permanent global ledger of the world's most important, most highly secured value storage system).
If the fees are not high enough to discourage every penny-ante gambler from yelling to the world about each and every few-penny bet they lose then the fees are probably too low.
-MarkM-
+1
Facilitating a dopey penny-ante gambling platform is hardly worth the cost of chasing people who might wish to operate transfer nodes (and thus be 'peers' in the supposedly p2p solution) to my way of thinking.
If it takes higher fees to discourage pointless dust, I'm for it...with some regret. Other more theoretical forms of addressing scaling issues do not seem forthcoming. A second best would be to chase small fry into other crypto-currency solutions and have Bitcoin proper evolve into a backing store platform for 'the elite.'
I just fired up my client after a year of down-time (thinking about digging into some of my deep storage loot to re-coup my initial outlay) and it has been catching up on the block chain for 4 days now. Not only that, but it's sucking the life out of my 4G i5 main workstation like no other software I've run. To be fair, it's a pretty old build of bitcoind however. Once I confirm that my some of my deep storage value is able to be re-couped, I'll try to build bitcoind from head again and see if the new database scheme is more efficient.