Apple releases Safari 3.1
macworld.com
Apple releases Safari 3.1
1–10 of 20 posts
Re: Apple releases Safari 3.1
#2Re: Apple releases Safari 3.1
#3Okay, I'm done venting now. Back to work sans 3.1...
Re: Apple releases Safari 3.1
#4bah! A required restart to upgrade a web browser?!?! I switched to OS X to avoid handcuffs such as this! Okay, I'm done venting now. Back to work sans 3.1...
Re: Apple releases Safari 3.1
#5Re: Apple releases Safari 3.1
#6bah! A required restart to upgrade a web browser?!?! I switched to OS X to avoid handcuffs such as this! Okay, I'm done venting now. Back to work sans 3.1...
I was shocked too. I didn't need to restart for the last iTunes update, but I did for Safari! What gives?
edit: maybe 'entire OS' was a little vague. basically they don't want to run into issues where the webkit gets updated and things that rely on webkit don't get all messed up in the process because they are running too.
Re: Apple releases Safari 3.1
#7Earlier quoted context omitted.
I was shocked too. I didn't need to restart for the last iTunes update, but I did for Safari! What gives?
webkit is an underlying framework that the entire OS uses. The nightly webkit rebuilds don't require a restart because they are sandboxing the webkit, but when apple updates safari it has to reboot the machine to initiate the new build of webkit to be used for the entire OS (including dashboard and things like that) edit: maybe 'entire OS' was a little vague. basically they don't want to run into issues where the web…
Re: Apple releases Safari 3.1
#8I started using Safari 2 on XP a few weeks ago and have been thoroughly impressed with it - it is now my default browser mainly because of its speed and look. There is one problem though that makes no sense: it cannot open an image file link within the browser - it has to open another app. This is especially problematic as my webapp is loaded with images I need to quickly open. I just got 3.1, and wow!, it is fast -…
Re: Apple releases Safari 3.1
#9Re: Apple releases Safari 3.1
#10Earlier quoted context omitted.
webkit is an underlying framework that the entire OS uses. The nightly webkit rebuilds don't require a restart because they are sandboxing the webkit, but when apple updates safari it has to reboot the machine to initiate the new build of webkit to be used for the entire OS (including dashboard and things like that) edit: maybe 'entire OS' was a little vague. basically they don't want to run into issues where the web…
the browser infrastructure is at the OS level? uh oh, didn't that get MSFT in trouble (it wasn't the only thing, but it was a signficant part of the charges)?
WebCore is a layout, rendering, and DOM library for HTML and SVG developed by the WebKit project, originally developed by Apple as a fork of KHTML. It is licensed under the LGPL. The WebKit framework wraps WebCore and JavaScriptCore, providing an Objective-C application programming interface to the C++-based WebCore rendering engine and JavaScriptCore script engine, allowing it to easily be referenced by Cocoa-based applications; later versions also include a cross-platform C++ platform abstraction, and various ports provide additional APIs.
end quote
basically it has to update and restart so that all cocoa based apps can use the new version.