Regarding point 2: what if Tesla pushed silent OTA updates for A/B test that accidentally disabled ABS or traction control, rendering the car unusable?
This is what I cannot grasp about modern software project management/ops. <s> The only relevant measure is time to ship. If the unit tests pass it is good to go. </s> So many times have I seen webapps so broken that core functions do not even load or by no means would pass simple "click here and there" usability test. In house QA sometimes seems to be abandoned. Automated testing is a good thing, but in my book shipping comes with implicit assertion that changes perform the task at least on a basic level.
Field A/B testing of experimental features is a good thing, which I am ok with even if I happen to get worse alternative. Shipping outright broken features if I am not on beta/testing/nightly release channel is unacceptable.
Re:WTF? Chromium (2016)
by FascinatedBox on Wednesday November 08, 2017 @01:04AM
(#15650203)
What other serious alternatives are out there though? I know of Firefox and Edge. But aren't Opera and Safari now reskins of Chromium, to some degree?
Re:WTF? Chromium (2016)
by dragonwriter on Wednesday November 08, 2017 @01:08AM
(#15650221)
Blink (Chromium’s engine) was forked from WebKit (Safari’s Engine) and the two have developed separately. Safari is not a skin of Chromium or vice versa.
2. You get the browser for free. If everyone adopted this same attitude, Chrome would not be able to do real-world A/B testing on features; what should they do instead, just release it all or nothing? You might have been unlucky today, but perhaps tomorrow someone else's misery provides the needed data to prevent a bad feature from going out.
3. Vote with your "feet", and switch to Firefox? (or one of the other myriad of browsers out there…)