As long as features can be simulated adoption will stagnate. As much as we like to think we (the developers) are in control of browser adoption, the simple real

As long as features can be simulated adoption will stagnate. As much as we like to think we (the developers) are in control of browser adoption, the simple reality is that we're not. The end users are. The "normals". They don't give a shit if your box-shadow uses a PNG or is implemented using CSS3. They don't know the difference between canvas and flash. Hey! it works right? I honestly believe that the way to move the web forward is by letting browsers innovate at the expense of standards, and for developers to adopt non-aesthetic API's that will cause functional differences from the stagnating dominant incumbent if there is one at the time (at the moment IE). In other words, when developers get pissed, they find solutions. When end users get pissed, the switch browsers, or decide your app is not worth it. Our goal is to get that proposition in front of end users as often as possible, and create enough value that they choose the former.