3 ms·
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 unaccepta
by Bartweiss 10y ago
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.
- greenyoda 10y ago"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.
- Bartweiss 10y agoI 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.