News for hackers. Stuff that matters.

A comment on Chromium/Blink – Intent to Implement: Experimental Framework. Parent comment

Re:Chromium/Blink – Intent to Implement: Experimental Framework by lucideer on Sunday October 11, 2015 @06:55PM (#10371469)
The benefit would be that - assuming the developer is well aware of this limitation - it would act as a disincentive to push code relying on the experimental feature to production.

It would however introduce a lot of hassle in testing the feature - being unable to work on a particular branch for all of every Tuesday. A better approach might be disabling it for an hour or two daily at 4am local time, or for 5 minutes per-hour, etc.

[ Parent | on HN ]
Re:Chromium/Blink – Intent to Implement: Experimental Framework by scottfr on Sunday October 11, 2015 @07:28PM (#10371616)
Doesn't having to ask your users to go to chrome://flags and click the "Enable" button next to some very scary looking technical text have the same effect?

I can't imagine asking users (either public or internal) to do that.

[ Parent | on HN ]
Re:Chromium/Blink – Intent to Implement: Experimental Framework by newjersey on Monday October 12, 2015 @01:42AM (#10372748)
We could just ask IT to set up flags on internal applications/users if there was a business need...
[ Parent | on HN ]