On 2014-04-16, 11:38 AM, Anne van Kesteren wrote:
On Wed, Apr 16, 2014 at 12:43 AM, Andreas Gal <andreas....@gmail.com> wrote:
Innovation happens all over the place, and we iterate towards a stable,
standardized point after innovation happened.
One of the problems we face with iterating towards that standardized
platform is legacy. https://hsivonen.fi/vendor-prefixes/ has a good
summary of it. That's why there might be some pushback.
If we want to continue to push the boundaries (and I agree we should),
we should also have some story around our APIs. We have
https://wiki.mozilla.org/WebAPI/ExposureGuidelines but it might not be
adequate here.
One approach could be that we clearly market the API as experimental
and purposefully break it every other release.
I think a great way to deal with that is to keep features on the beta
channel and continue to make breaking changes to them before we feel
ready to ship them. The reality is that once we ship an API our ability
to make any backwards incompatible changes to it will be severely
diminished if websites that our users depend on break because of that
(albeit in the case of a very new technology such as VR which will not
be useful on all Web applications, the trade-off might be different.)
Cheers,
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
