Unfortunately most of the real discussion will be lost in a flood of worthless HTML5 x Flash war discussions by overexcited zealots, but this is great news both

Unfortunately most of the real discussion will be lost in a flood of worthless HTML5 x Flash war discussions by overexcited zealots, but this is great news both for developers and users alike: not because of Flash integration itself (although it's good to have a plugin always updated), but because of the new browser plugin api being proposed. This is something that has been long overdue, and something that will benefit users as a whole in allowing a more tight control of what a plugin does, and how. Think of all the interface integration problems we currently have with plugins (any plugin), from performance problems (when a plugin can't have control over what kind of resources it actually has allocated), to input problems (should/can the plugin trap shortcuts and special keys, or the scroll bar?), to device control (who controls the volume of the sound used by the plugin?). Hopefully, these will all soon be a problem of the past, as Chrome (and others) adopt the new plugin API, and we can all move on to a more well-integrated web experience.