That raises an excellent point! I would extend those compile time flags to
include prevent experiments from getting into beta/stable as well.
Kind Regards,
Anthony Laforge
Technical Program Manager
Mountain View, CA
On Mon, Sep 21, 2009 at 2:31 PM, Jeremy Orlow jor...@chromium.org wrote:
I
It is really useful to have early code compiling and running as much
as possible on all platforms right from the beginning. This catches a
lot of issues early in the development cycle and prevents scary
monolithic integration phases.
Could we also fix this problem by doing something in the
On Mon, Sep 21, 2009 at 2:31 PM, Jeremy Orlow jor...@chromium.org wrote:
I think we need to re-consider our practice of shipping beta/stable
browsers with experimental features hidden behind flags--at least when they
have any side-effects in JavaScript. An example of where this has bitten us
On Mon, Sep 21, 2009 at 2:47 PM, Aaron Boodman a...@chromium.org wrote:
It is really useful to have early code compiling and running as much
as possible on all platforms right from the beginning. This catches a
lot of issues early in the development cycle and prevents scary
monolithic
On Mon, Sep 21, 2009 at 2:55 PM, Jeremy Orlow jor...@chromium.org wrote:
On Mon, Sep 21, 2009 at 2:47 PM, Aaron Boodman a...@chromium.org wrote:
It is really useful to have early code compiling and running as much
as possible on all platforms right from the beginning. This catches a
lot of
On Mon, Sep 21, 2009 at 2:31 PM, Jeremy Orlow jor...@chromium.org wrote:
I think we need to re-consider our practice of shipping beta/stable
browsers with experimental features hidden behind flags--at least when they
have any side-effects in JavaScript. An example of where this has bitten us
On Mon, Sep 21, 2009 at 3:29 PM, John Abd-El-Malek j...@chromium.org wrote:
On Mon, Sep 21, 2009 at 2:31 PM, Jeremy Orlow jor...@chromium.org wrote:
I think we need to re-consider our practice of shipping beta/stable
browsers with experimental features hidden behind flags--at least when
On Mon, Sep 21, 2009 at 3:43 PM, Jeremy Orlow jor...@chromium.org wrote:
On Mon, Sep 21, 2009 at 3:29 PM, John Abd-El-Malek j...@chromium.orgwrote:
On Mon, Sep 21, 2009 at 2:31 PM, Jeremy Orlow jor...@chromium.orgwrote:
I think we need to re-consider our practice of shipping beta/stable
On Mon, Sep 21, 2009 at 3:51 PM, John Abd-El-Malek j...@chromium.org wrote:
On Mon, Sep 21, 2009 at 3:43 PM, Jeremy Orlow jor...@chromium.org wrote:
On Mon, Sep 21, 2009 at 3:29 PM, John Abd-El-Malek j...@chromium.orgwrote:
On Mon, Sep 21, 2009 at 2:31 PM, Jeremy Orlow
On Mon, Sep 21, 2009 at 3:59 PM, Jeremy Orlow jor...@chromium.org wrote:
On Mon, Sep 21, 2009 at 3:51 PM, John Abd-El-Malek j...@chromium.orgwrote:
On Mon, Sep 21, 2009 at 3:43 PM, Jeremy Orlow jor...@chromium.orgwrote:
On Mon, Sep 21, 2009 at 3:29 PM, John Abd-El-Malek
I agree. Our practice of releasing experimental features default disabled
behinda command line flag is extremely valuable. We should make sure that
this works
well for new web APIs. It will continue to be a valuable tool down the
road.
It is important that we have features available in stable,
All right. I'm not 100% convinced, but either way I think we need to
understand better how to remove these features' side-effects from JavaScript
when disabled.
Mads (or anyone else) can you provide any thoughts on how we can implement
the following in our bindings generator?
(1) We need to be
--
From: Drew Wilson atwil...@google.com
Date: Mon, Sep 21, 2009 at 5:03 PM
Subject: Re: [chromium-dev] Shipping features behind a run-time flag can
sometimes still be dangerous
To: Mike Belshe mbel...@google.com
On Mon, Sep 21, 2009 at 2:52 PM, Mike Belshe mbel...@google.com wrote:
On Mon
Indeed. BTW I filed http://crbug.com/18577 so it'd be easier to find (and
copy-paste) the command line flags used for a build. We can add this to the
default template if it'd be useful.
-Ben
On Mon, Sep 21, 2009 at 4:37 PM, Darin Fisher da...@chromium.org wrote:
I agree. Our practice of
14 matches
Mail list logo
