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.
Re:Cross-platform web design issue
by
Anonymous Coward
·
· Score: 2, Insightful
Yes. Design them for and look at them with a standards-compliant Windows browser, not that piece of shit MSIE.
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.
Re:Cross-platform web design issue
by
cloudless.net
·
· Score: 2, Insightful
Being standards compliant doesn't ensure my design will look right in Safari. Every browser has its own bugs and quirks, CSS2 is an established standard, but even Mozilla can't completely handle it. That's why it is important to test the design in different browsers.
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
Don't get 10.2!
by
littleghoti
·
· Score: 2, Insightful
I'd wait for 10.3 if I were you. Get the panther goodness later in the year with all the new stuff, and pay only once.
Re:Good stuff
by
Farley+Mullet
·
· Score: 2, Insightful
I bet Apple already knew IE would be gone on Mac OS, before starting to develop Safari.
Yeah, but I bet developing the iTunes Music store, with its need for embedded HTML rendering, had more to do with do with developing Safari and the WebCore stuff.
Tab support is kind of cobbeled
by
Bakafish
·
· Score: 2, Insightful
The problem is that unlike Mozilla based browsers the tabs don't support drag and drop URL's so you aren't able to reuse them. I like to drag links to existing tabs to update them with new information, or drag a URL to the empty tab area to create a new tab.
You can drag links between windows, why not between tabs? At least make the tabs 'spring loaded' or something.
Slashdot Mirror
Yes. Design them for and look at them with a standards-compliant Windows browser, not that piece of shit MSIE.
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
Being standards compliant doesn't ensure my design will look right in Safari. Every browser has its own bugs and quirks, CSS2 is an established standard, but even Mozilla can't completely handle it. That's why it is important to test the design in different browsers.
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
I'd wait for 10.3 if I were you. Get the panther goodness later in the year with all the new stuff, and pay only once.
Yeah, but I bet developing the iTunes Music store, with its need for embedded HTML rendering, had more to do with do with developing Safari and the WebCore stuff.
The problem is that unlike Mozilla based browsers the tabs don't support drag and drop URL's so you aren't able to reuse them. I like to drag links to existing tabs to update them with new information, or drag a URL to the empty tab area to create a new tab.
You can drag links between windows, why not between tabs? At least make the tabs 'spring loaded' or something.
Anyway, otherwise it is a great little browser.