Arg. Fine, I'll lay off the opinionating and simply use facts. I warn that it is far less colourful reading.
On the PHP4 to PHP5 change: the error that most commonly broke PHP apps was the allow_call_time_pass_reference setting. In the PHP ini file, since 4.0-ish, it has stated clearly that having that turned on would *not* be supported in the future. This was an override behaviour that was being deprecated in future versions (and clearly noted as such), but was still taken advantage of extensively by many (or possibly most) PHP devs. So WP broke if this was turned off (the default value as of 4.1 or thereabouts). The fix is easy, and it was done for *most* projects (including WP) very quickly.
On the MySQL 4 to 5/strict change: this is simply (mostly) a matter of properly inserting rows into the database. Strict mode simply changes many warnings into errors. There is no other behavioural change that affects WP (that I know of), since 5.0x is primarily a feature-addition/bug-fix version. This error is the only one I see in both 1.5.2 and 2.0B2 (and SK2, incidentally). Turning strict-mode off corrects the problem. Again, how hard is it to write valid SQL? I've written a *lot* of SQL for MySQL, SQL Server, and Oracle, and I've never seen this error before. Just make sure the inserts are valid (based on the table schema), and this problem goes away.
So yes, I would like to see this bug fixed. If I have time this weekend or during the week, I'll grab the latest from SVN and see if I can do it myself. I'm not all that educated in PHP, but I'll give it a go if no one else will.
