Live data from Hacker News

Apple releases Safari 3.1

macworld.com

1–10 of 20 posts

Re: Apple releases Safari 3.1

#2
I have been really impressed with what webkit has been doing. They seem like they are really striving to be the best browser in the market. Their nightly builds have been extremely quick and bug free recently and i'm glad that apple decided to release a newer version out into the wild.

Re: Apple releases Safari 3.1

#4
post #3

bah! 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?

Re: Apple releases Safari 3.1

#5
I 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 - seriously (on windows xp). The install was fast. But no opening image files within the browser - what are they thinking? (I'm still using it though)

Re: Apple releases Safari 3.1

#6
post #3

bah! 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?

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 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

#7

Earlier 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…

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)?

Re: Apple releases Safari 3.1

#8
post #5

I 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 -…

I've never had that problem, did quicktime do something terrible to you? Point to this doll of your mime types, and show me where the bad man touched you.

Re: Apple releases Safari 3.1

#9
Funny because just 2 days ago I switched to FF3b4 because Safari was crashing too often on flash-based ads (of all things!). Now I'm switching back to Safari, even though FF3 is pretty cool, because it just handles (scrolls, renders, feels) faster and smoother.

Re: Apple releases Safari 3.1

#10
post #7

Earlier 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)?

from wikipedia: WebCore

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.

Post reply on HN