3 ms·
Couple of corrections. - Apple didn't license WebKit. Apple created WebKit, by forking Konqueror's engine. - Chrome doesn't update without restarting. (Unless
by hackmiester 13y ago
Couple of corrections.
- Apple didn't license WebKit. Apple created WebKit, by forking Konqueror's engine.
- Chrome doesn't update without restarting. (Unless you mean restarting the machine, in which case, of course not! What kind of browser would require a machine reboot to... oh.)
- dualogy 13y ago> Apple didn't license WebKit. Apple created WebKit, by forking Konqueror's engine Of course, you're right. I was typing this faster than I was thinking.. Anyway, MS shouldn't even think of pulling something like this, on second thought---because rather than a render-engine replacement, it would end up as yet another "mode" in IE.. > Chrome doesn't update without restarting Of course the binary cannot replace itself while running -- ((although with each tab being its own process and their highly persistent statefulness they might consider silently "rebooting" background tabs)) -- but, well at my end / from my experience, Chrome doesn't restart itself and doesn't prompt about restarting, in most cases -- rather seems to wait until the next time it is restarted by the user. Maybe I get that wrong, but if my memory recalls this as Chrome's auto-update user-experience, that's a feat one way or the other..
- stan_rogers 13y agoChrome will display an update arrow on the menu/address bar. If you haven't restarted in a while, it will eventually become a rather insistent red.
- oneeyedpigeon 13y agoWow, you mean you've had the patience and lack of ADD to wait a certain period of time without clicking the arrow? You're zen, my friend :)