optikz writes "Apple has just released Safari 1.0 and it is availlable via Software Update. This release is now out of the 'beta' stage. It is version 1.0 (v85)." Not much appears to have changed since the last beta. I just need to decide if it should replace Camino for me.
Nearly perfect timing, too. IE's gone, Safari's here... out with the old, in with the new.
Re:Good stuff
by
cloudless.net
·
· Score: 5, Interesting
I bet Apple already knew IE would be gone on Mac OS, before starting to develop Safari.
Seems faster
by
Llywelyn
·
· Score: 4, Informative
While I don't have any benchmarks, it seems faster and more responsive overall. This wouldn't surprise me, since they've probably removed a good deal of the debug code.
It still has a bad habit of trying to deeplink itself into CNN every time I go there and a few rendering fragments when a text box crosses the address/status bar, but other than that it seems very solid as a release.
There are no real improvements in the prefs panel since last time either, which is unfortunate.
Cross-platform web design issue
by
cloudless.net
·
· Score: 4, Interesting
I think Safari will gain popularity quickly, I would like my web pages to look good in that browser. However I only have a Windows box, is there anyway I can see how my web pages look in Safari while I am running Windows?
Re:Cross-platform web design issue
by
thumperward
·
· Score: 4, Informative
Webcore renders in a similar way to Gecko. If you absolutely must know how it renders in Safari though, get a Knoppix CD and check with Konqueror.
- Chris
Some stuff still needs fixin'
by
phillymjs
·
· Score: 4, Interesting
The only problems I have with Safari are:
1) It does not render the Outlook Web Access from Exchange 2000 properly. This may just be because those Microsoft ass-clowns have coded it specifically for IE, it may not be Safari's fault.
2) One of my larger corporate clients uses some crap web proxy that Safari doesn't like-- http sites load okay, but https sites do not work at all. They don't even try to load. I dunno if there's some authentication issue or what, but I know all my settings are set properly, and everything authenticates fine for http. One of these days perhaps I'll steel myself to talk with one of the corporate help desk script monkeys and see if I can't find out what proxy it is so I can submit a bug report.
~Philly
Re:Some stuff still needs fixin'
by
bedouin
·
· Score: 4, Informative
http sites load okay, but https sites do not work at all.
Just curious, have you tried it recently? There was a bug in early builds of Safari where secure proxies simply didn't work; it's since been fixed.
Either that or they got tired of waiting.
by
Llywelyn
·
· Score: 4, Insightful
It is also possible that they just got sick of waiting for a good, standards-complient web-browser or that they got sick of being so dependent on MS for a decent browser.
Camino and Mozilla weren't quite up to snuf and have serious flaws, as things are; IE was years behind everything else, was too slow, poorly threaded, and had a host of other issues... OmniWeb and Standard Compliance didn't belong in the same sentence--particularly when it came to CSS, and Opera just plain Sucked on the Mac.
The rational choice, particularly for such an important app as a web browser, is in-house development.
The default font has also changed to Times. Pages rendered look much more like IE now.
Re:Still a little buggy
by
babbage
·
· Score: 4, Informative
Don't tell us -- file a bug! If you had it active before, the "bug" icon may have gone away with the 1.0 upgrade, but it can be restored, and "Repot bugs to Apple..." is still the second item under the Safari menu.
The Safari group has been responsive to bug fixes so far, and hopefully will continue to be now that the first milestone release is out of the way.
I still wish that yo ucould tab to all active page elements, not just text fields. Must go submit that one myself...
Re:On-line banking?
by
djupedal
·
· Score: 4, Funny
I can get into your account with it, no issue:) - Man, you have got to do a better job saving...
Safari is off to an excellent start
by
King+Babar
·
· Score: 4, Insightful
It really is very impressive, but Jobs is being...cheeky when he claims it is the best browser on any platform. Camino and Mozilla are still competitive, and that's a great thing. Where Safari can do better is in filling in support for features where it is already strong.
So, for example, Safari provides very good support for @media style rules, but (oddly) doesn't support things like the "page-break-before" property or @page {size: landscape}. This is a bit surprising, and I'd like to see Safari reduce the number of surprises in general.
Mozilla can learn from Safari, as well. Safari's bookmark system is better. It's tabbed browsing implementation is nicer. I suspect these features will be adapted into other browsers, and as the competition heats up again (now that the IE giant is sleeping), everybody wins.
--
Babar
RAM Disk in OS X and how to move Safari's cache
by
SensitiveMale
·
· Score: 5, Informative
70% of this code isn't mine, but found I bits everywhere.
The first part is a AppleScript. It does a few things. First it creates the RAM disk. Then it renames the RAM disk. Then it automatically starts Safari. The reason why I have it start Safari is to ensure the RAM disk is up and running at login before Safari is launched.
Where you see the line "set diskSize to 40" sets the RAM disk's size. 40 is 40 Megs. Simply change that to whatever size you want.
Copy and paste the script into the script editor, Save it as "application" and be sure to uncheck the box "Never show startup screen".
tell application "Finder"
activate
set diskSize to 40
set diskSize to diskSize * 2048
do shell script "hdid -nomount ram://" & diskSize
set dskImg to the result
set prevTextDelims to AppleScript's text item delimiters
set AppleScript's text item delimiters to {"/"}
set myDevDisk to the last text item of dskImg
set myShellCmd to "/sbin/newfs_hfs/dev/r" & myDevDisk as text
do shell script myShellCmd
do shell script "hdiutil mount/dev/" & myDevDisk
set AppleScript's text item delimiters to prevTextDelims
end tell
delay (1)
tell application "Finder"
set name of item "untitled" to "RAM Disk"
end tell
tell application "Safari"
launch
end tell
Here is how you move Safari's cache to the RAM Disk.
Then delete the folder "your home/library/caches/safari"
Run this command -
ln -s "/Volumes/RAM Disk" ~/Library/Caches/Safari
That will create the link between the RAM disk and your safari cache folder.
That's it. Works perfectly and much much faster.
You will have to run the applescript at login.
You only have to run the terminal commands once.
Re:What was the default font before?
by
ProfKyne
·
· Score: 4, Informative
You guys are still all wrong about that. The serifs were used in print in an attempt to replicate the carved stone lettering that adorned buildings and stone-cut signs. And the reason why those serifs appeared (on stone-cut signs) was because the stone was often very brittle and would crumble at the corners of the letters. So the stonecutters adopted a style that would still look good while accounting for this inadvertent crumbling.
My dad told me this when I was a kid. He got a master's degree in print technology from RIT -- I believe him.
-- "First you gotta do the truffle shuffle."
Re:What was the default font before?
by
switcha
·
· Score: 4, Interesting
with all due respect, I don't think we are hanging onto serifs because of old rocks. It's all because of readability.
Other factors such as leading and acender/decender height have a huge impact, but none as great as serif/san-serif.
I too, have a degree in printing, and have had textbook after texbook after teacher beat me over the head with case studies in readability.
Especially that slab-serifs (where the serifs and bars have a minimal difference) are kings of readability.
This piece brings up anther interesting factor. Not only are serifs supposedly physically easier to follow in long text, but according to the piece, there is a cultural component as well.
I'm not sure how completely I buy that, as I have read texts citing all sorts of optical testing of jabber text and controls to ensure unfamiliarity. And serif comes out more readable. You can debate whether bylines, captions, or headlines should be serif or san, but try reading Moby Dick in Futura and then after your eyes stop cramping, we'll talk.
-- You know what?... A little club soda *did* get that out!
Slashdot Mirror
Nearly perfect timing, too. IE's gone, Safari's here ... out with the old, in with the new.
While I don't have any benchmarks, it seems faster and more responsive overall. This wouldn't surprise me, since they've probably removed a good deal of the debug code.
It still has a bad habit of trying to deeplink itself into CNN every time I go there and a few rendering fragments when a text box crosses the address/status bar, but other than that it seems very solid as a release.
There are no real improvements in the prefs panel since last time either, which is unfortunate.
Integrate Keynote and LaTeX
I think Safari will gain popularity quickly, I would like my web pages to look good in that browser. However I only have a Windows box, is there anyway I can see how my web pages look in Safari while I am running Windows?
The only problems I have with Safari are:
1) It does not render the Outlook Web Access from Exchange 2000 properly. This may just be because those Microsoft ass-clowns have coded it specifically for IE, it may not be Safari's fault.
2) One of my larger corporate clients uses some crap web proxy that Safari doesn't like-- http sites load okay, but https sites do not work at all. They don't even try to load. I dunno if there's some authentication issue or what, but I know all my settings are set properly, and everything authenticates fine for http. One of these days perhaps I'll steel myself to talk with one of the corporate help desk script monkeys and see if I can't find out what proxy it is so I can submit a bug report.
~Philly
It is also possible that they just got sick of waiting for a good, standards-complient web-browser or that they got sick of being so dependent on MS for a decent browser.
Camino and Mozilla weren't quite up to snuf and have serious flaws, as things are; IE was years behind everything else, was too slow, poorly threaded, and had a host of other issues... OmniWeb and Standard Compliance didn't belong in the same sentence--particularly when it came to CSS, and Opera just plain Sucked on the Mac.
The rational choice, particularly for such an important app as a web browser, is in-house development.
Integrate Keynote and LaTeX
The default font has also changed to Times. Pages rendered look much more like IE now.
The Safari group has been responsive to bug fixes so far, and hopefully will continue to be now that the first milestone release is out of the way.
I still wish that yo ucould tab to all active page elements, not just text fields. Must go submit that one myself...
DO NOT LEAVE IT IS NOT REAL
I can get into your account with it, no issue :) - Man, you have got to do a better job saving...
So, for example, Safari provides very good support for @media style rules, but (oddly) doesn't support things like the "page-break-before" property or @page {size: landscape}. This is a bit surprising, and I'd like to see Safari reduce the number of surprises in general.
Mozilla can learn from Safari, as well. Safari's bookmark system is better. It's tabbed browsing implementation is nicer. I suspect these features will be adapted into other browsers, and as the competition heats up again (now that the IE giant is sleeping), everybody wins.
Babar
70% of this code isn't mine, but found I bits everywhere.
/dev/r" & myDevDisk as text /dev/" & myDevDisk
The first part is a AppleScript. It does a few things. First it creates the RAM disk. Then it renames the RAM disk. Then it automatically starts Safari. The reason why I have it start Safari is to ensure the RAM disk is up and running at login before Safari is launched.
Where you see the line "set diskSize to 40" sets the RAM disk's size. 40 is 40 Megs. Simply change that to whatever size you want.
Copy and paste the script into the script editor, Save it as "application" and be sure to uncheck the box "Never show startup screen".
tell application "Finder"
activate
set diskSize to 40
set diskSize to diskSize * 2048
do shell script "hdid -nomount ram://" & diskSize
set dskImg to the result
set prevTextDelims to AppleScript's text item delimiters
set AppleScript's text item delimiters to {"/"}
set myDevDisk to the last text item of dskImg
set myShellCmd to "/sbin/newfs_hfs
do shell script myShellCmd
do shell script "hdiutil mount
set AppleScript's text item delimiters to prevTextDelims
end tell
delay (1)
tell application "Finder"
set name of item "untitled" to "RAM Disk"
end tell
tell application "Safari"
launch
end tell
Here is how you move Safari's cache to the RAM Disk.
Close Safari.
Open terminal.
Run this command -
ditto -rsrc ~/Library/Caches/Safari "/Volumes/RAM Disk/"
Then delete the folder "your home/library/caches/safari"
Run this command -
ln -s "/Volumes/RAM Disk" ~/Library/Caches/Safari
That will create the link between the RAM disk and your safari cache folder.
That's it. Works perfectly and much much faster.
You will have to run the applescript at login.
You only have to run the terminal commands once.
You guys are still all wrong about that. The serifs were used in print in an attempt to replicate the carved stone lettering that adorned buildings and stone-cut signs. And the reason why those serifs appeared (on stone-cut signs) was because the stone was often very brittle and would crumble at the corners of the letters. So the stonecutters adopted a style that would still look good while accounting for this inadvertent crumbling.
My dad told me this when I was a kid. He got a master's degree in print technology from RIT -- I believe him.
"First you gotta do the truffle shuffle."
Other factors such as leading and acender/decender height have a huge impact, but none as great as serif/san-serif.
I too, have a degree in printing, and have had textbook after texbook after teacher beat me over the head with case studies in readability.
Especially that slab-serifs (where the serifs and bars have a minimal difference) are kings of readability.
This piece brings up anther interesting factor. Not only are serifs supposedly physically easier to follow in long text, but according to the piece, there is a cultural component as well.
I'm not sure how completely I buy that, as I have read texts citing all sorts of optical testing of jabber text and controls to ensure unfamiliarity. And serif comes out more readable. You can debate whether bylines, captions, or headlines should be serif or san, but try reading Moby Dick in Futura and then after your eyes stop cramping, we'll talk.
You know what?