1) Static JavaScript. Instead of using the *.js.php which I have been using, javascript templates are being parsed by a small JS templating engine and stored as static files. This should significantly cut down on the amount of time spent processing php. Each file is stored as filename-hashcode.js.

2) Bootstrapper. People have told me a) They don’t think it’s fair to count the size without jQuery (it probably isn’t) and b) They don’t want to load jQuery on every pageload. To that end, the default install will now include a tiny bootstrapper (hopefully under 200 Bytes) that doesn’t load the player until and unless someone actually wants to use them.

3) Single audio player. For legacy browsers, there will only be one player, the awesome Sound Manager 2 player. User interface will be provided via jQuery based controls. Using a single “invisible” player allows a consistent JavaScript interface for all the players, and, should help to

4) <audio> tag based player. This will probably be beta only in 0.7, but I want to move towards using the native browser implementation instead of flash. Using a javascript interface and sound manager means it should be a seamless user experience, and the only difference is whether the JavaScript is calling the sound manager js or the <audio> tag.

I’ll be at WordCamp in San Francisco this weekend, anyone who wants to bend my ear about a feature can do so. Twitter at jwriteclub to get together.