Sgt_Kickaxe - 8:23 am on Jun 19, 2010 (gmt 0)
32MB is the memory limit on some shared hosts. While 3.0 was being tested and tested and tested it wasn't small enough in size to be released. When testing was completed that problem was realized and the butcher job of cutting it to size began without re-testing prior to release. While I'm sure it's safe, for now, this type of lack of foresight (added to the dev team going ninja immediately after release instead of getting on top of issues) doesn't make me want to jump on board just yet.
You can read about the size problem and the butcher jobs proposed in the dev trac - [core.trac.wordpress.org...]
from the trac...
Losing tinymce.js and the importers bought us quite a bit of extra room. There will probably be some setups with lots of plugins and big po and mo files that will bust the limit, but there's only so much butchering we can do. The workaround is to do a manual upgrade. I think we've done enough here.
Doesn't inspire confidence.
Another last resort option: we could remove the Prototype.js/Scriptaculous (290KB) and load it from googleapis when queued from a plugin. It hasn't been used in core for a long time and don't think there are many plugins that use it.
Scriptaculous is actually pretty versatile, removing it for a Google dependent alternative isn't a great idea else plugins could go down due to Google changes which in turn could cause (unknown and untested) problems.
If nothing else, the hack job to cut it to size after testing was complete merrits a little "wait and see" in my opinion. 2.9.2 isn't broken yet.
I totally appreciate the effort these guys put into wordpress but it's code and needs to be done right including testing, no exceptions.
The final entry in this trac...
There's not much more we can do here for 3.0, which goes RC soon. Addressing root causes will have to wait for 3.1.
That speaks volumes, especially since 3.1 is being put off. Problems are known, no solutions were completed, instead some changes were made to mask the symptoms (according to the dev trac). What else isn't fully up to par? I'll let early adopters find out and wait for 3.1. Hopefully Google isn't quick to the punch with not up-to-date installation penalties (if there is such a thing).
leadegroot - give me a link to your site and I'll tell you what version it is, there is always a way to find out.