5 ms·

> Basically, they're moving to a standards-compliant model like WebKit or Gecko I think that was the professed and proclaimed goal for every IE version since 8

by dualogy 13y ago

> Basically, they're moving to a standards-compliant model like WebKit or Gecko I think that was the professed and proclaimed goal for every IE version since 8, or maybe even back at 7? I keep hearing that for years, and what this intention delivers in the end is yet more "IE modes": n "browser modes" times 2 "document modes". Quirks mode. "Compatibility view." So for IE 11, web developers would have two choices: test your page in a total of 10 IE mode-combinations. Or just serve "the Crawler/Geocities version of our site" to IE users no matter what version they're using. Which is of course what MS/IE wants to avoid. But hey they could just pull an "Apple Inc." and license WebKit, or pull a "Google Inc." and make your browser auto-updating. Without prompts, progress indicators or restarts, just as invisible and efficiently as Chrome does by default. Presto, no more headaches with IE for BOTH users AND web devs. Maybe some MS egos would get a little dent, maybe some enterprise consultancy shops would have to cut down on man-days sold for IE-specific work. Ah yes. I can see why IE won't go this way any time soon---or only way after it has been finally and fully obsoleted even in the remotes of backwater net-cafes and even the slowest of Enterprise-IT depts...

deleted 13y ago
[deleted]
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 ago
    Chrome 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 ago
      Wow, 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 :)
alipang 13y ago
Presto... :(
yuhong 13y ago
Well, remember that the IE components are global system files that require at least restarting Windows Explorer and often a reboot to update and all versions of IE follows the lifecycle of the underlying version of Windows. I have proposed rapid release IE in the past but it'd have to be separate from the current IE installation.

by dualogy 13y ago

deleted 13y ago

[deleted]

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 ago
  Chrome 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 ago
    Wow, 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 :)

alipang 13y ago

Presto... :(

yuhong 13y ago

Well, remember that the IE components are global system files that require at least restarting Windows Explorer and often a reboot to update and all versions of IE follows the lifecycle of the underlying version of Windows. I have proposed rapid release IE in the past but it'd have to be separate from the current IE installation.