Years ago I set up a site for a Club I belong to; I picked WordPress and went ahead and built a small site; it has a few dozen visitors a week; mostly it is an recruitment and contact/route guide for the club; and a place to dump odd photos and stories from members.
We have limited funds; whatever we do has to be cheap.
And now; wordpress will no longer run in the memory allocation we pay for; we can pay for more; or we can incur one-time charges and go to another provider; except that they all charge approximately the same. in summary: we cant get 64Mb hosting without doubling our costs.
I came here looking for some workarounds; maybe a few neat tricks, or a 'wait for release 2.x.0; we're going to properly allocate only memory we need then..' etc..
What I found is a an attempt to shoot the messenger; all threads are rapidly filled with non-viable solutions and criticisms of the posters and their hosting choices; and then closed to further comments to prevent the obvious withering replies.
This is a shame; it's sad to see an open source project going the Commercial path of bloat, indifference, transparent attempts to control the agenda and public denial of problems.
The better solution is to do a proper audit of memory allocation in the WordPress core and pare it down to the minimum necessary. People will still have problems with poor plugins; but these can be disabled and addressed through their developers, or abandoned, whereas the WP core cannot.
To put it in perspective: If I tar up (make an uncompressed archive of) my entire WP install, including 11 Db backups and the uploads folder, it is smaller than the memory footprint of that same install while running with all plugins disabled.
My solution is to revert to 2.7.1 and start looking for a WP replacement with a future.