You know what? Most browsers are developed pretty much entirely in line with the agile manifesto; most have either quick releases or a permanently stable master branch (to use git parlance!).
The issue isn't in shipping browsers which support unprefixed properties, the issue is:
- Dropping prefixed forms (which is basically not happening in WebKit, as Apple is scared of breaking non-web content, and they have no way to tell who is using WebKit within an application for bundled content and who is using it for the web) which means web developers have no encouragement to move to the prefixed forms.
- The convoluted specification of CSS which means people frequently find bizarre, bad interactions with other parts of the specification which people want to work out before shipping.
- The inability to drop anything once shipped: once something is shipped in a web browser, sites often start relying upon it (even if it isn't interoperable, behind UA-sniffing), which makes it hard to drop (users don't like sites breaking, and most applications need users to have a viable business model), and hence makes a lot of pressure to get it right first time, giving very little space to iterate.
- W3C policies which care about the patent policy and having a stable specification everyone can implement perfectly than about continual iteration.
The issue isn't in shipping browsers which support unprefixed properties, the issue is:
- Dropping prefixed forms (which is basically not happening in WebKit, as Apple is scared of breaking non-web content, and they have no way to tell who is using WebKit within an application for bundled content and who is using it for the web) which means web developers have no encouragement to move to the prefixed forms.
- The convoluted specification of CSS which means people frequently find bizarre, bad interactions with other parts of the specification which people want to work out before shipping.
- The inability to drop anything once shipped: once something is shipped in a web browser, sites often start relying upon it (even if it isn't interoperable, behind UA-sniffing), which makes it hard to drop (users don't like sites breaking, and most applications need users to have a viable business model), and hence makes a lot of pressure to get it right first time, giving very little space to iterate.
- W3C policies which care about the patent policy and having a stable specification everyone can implement perfectly than about continual iteration.