Re:Don't tug on that, you never know what it might be attach...
by Bartweiss on Friday July 01, 2016 @11:45PM
(#12021293)
I think this is a serious issue, at least for developers. I've never been burned by a self-updating browser, but anything beyond that seems downright unacceptable. There are just too many fragile, hand-managed dependency chains at work even in good setups.
[ Parent
| on HN ]
Re:Don't tug on that, you never know what it might be attach...
by greenyoda on Saturday July 02, 2016 @12:34AM
(#12021382)
"I've never been burned by a self-updating browser..."
I develop browser-based software which, after one Chrome update, was rendered unusable by a bug in Chrome. Fortunately, Google pushed out a new version with a fix the next day.
Re:Don't tug on that, you never know what it might be attach...
by Bartweiss on Sunday July 03, 2016 @06:10PM
(#12027865)
I did suspect that "I've never been burned" just meant I hadn't developed enough for browsers...
This also seems like a good reminder that transparent updating only works if your team is good and responsive enough to fix mistakes on the fly. If you're rolling out one update a month, you'd better give people a choice so they can decline when you hand them faulty upgrades.