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.
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.
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.
Slashdot Mirror
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
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