Slashdot Mirror


Safari 3 vs. Firefox 2 and IE7

Bobcat writes "Ars Technica has a 'first look' at Safari for Windows, which is interesting because it's written from the perspective of someone new to Safari. It was tested against Firefox 2 and IE7 and aside from the slightly faster page loading, Ars didn't find much to recommend it to Windows users. 'The modest increase in rendering performance is hardly worth the deficiencies, and Safari's user interface simply doesn't provide the usability or flexibility of competing products. If the folks at Apple think that providing Windows users with a taste of Mac OS X through Safari is going to entice them to buy a Mac, it's going to take a better effort than the Safari 3 beta. Even if the final release is more polished and completely bug-free, it still won't be as powerful or feature-loaded as Opera or Firefox.'"

25 of 559 comments (clear)

  1. Pshhh... by Mockylock · · Score: 5, Funny

    I prefer Netscape Navigator 1.0. Simple, yet barely useable.

    --
    "Please, shut up. Just when I think you can't say anything more stupid, you speak again." -Archie Bunker.
    1. Re:Pshhh... by jdray · · Score: 5, Funny

      Links? Slacker! In my day, we read the HTML document raw. We had to interpret the tags ourselves. No DNS, either. We kept lists of IP addresses written on shirtsleeves. And they weren't our shirtsleeves, either. We had to steal them from our neighbors...

      --
      The Spoon
      Updated 6/28/2011
    2. Re:Pshhh... by Bob-taro · · Score: 5, Informative

      It's been 3 minutes, I can't believe no one's corrected you yet ... It's EBCDIC.

      --
      Prov 9:8 Do not rebuke mockers or they will hate you; rebuke the wise and they will love you.
    3. Re:Pshhh... by oliverthered · · Score: 5, Funny

      You had it easy, back in my day we had to post all our data on punch cards, send them off, wait a week, hope there wasn't a error in our request and then read the HTML back one like a time

      --
      thank God the internet isn't a human right.
    4. Re:Pshhh... by Lillesvin · · Score: 5, Funny

      $ telnet slashdot.org 80
      GET / HTTP/1.0
      Host: 127.0.0.1

      ...

      Human parsing FTW! :-p

      --
      "Live free or don't."
    5. Re:Pshhh... by Lemmeoutada+Collecti · · Score: 5, Funny

      Shoot kid, back when I started using these computer things, we had to send a fox to the guy with the server, with or without a rock (we called em bits) tied to it's back. With a rock was one bit, without a rock was 0 bits. Then he would send the fox back, with or without the bit on it's back.

      Sometimes the fox would lose the bit, that was a dropped bit. We had a lot of dropped bitsback then. And man in the middle attacks, those danged nobles liked to hunt our foxes and take our bits for themselves. We quickly learned not to send coins as bits, as those financial transactions were always targets of those horse riding hackers.

      All that foxing back and forth was great high tech stuff, though. It meant that we could find out what happened to the hero in our latest serial we were following. Stories over fox took a while to load, but no longer than a torrent does now days... about two weeks to the chapter.

      Then some smarty came up with a bit bag, which we could put several bits in at a time, and send the whole packet with the fox. Then packet loss became a bigger problem, but bit loss pretty much disappeared.

      You kids now days with your quality of service and TCP/IP. You don't know how good you have it!

      Now get off'n my lawn!

      --

      You can have it fast, accurate, or pretty. Pick any 2.
    6. Re:Pshhh... by Dolly_Llama · · Score: 5, Funny

      In my day, we read the HTML document raw. We had to interpret the tags ourselves.


      So that's what the blink tag was for...
      --

      Somewhere, something incredible is waiting to be known. -- Carl Sagan

  2. Is he kidding? by d474 · · Score: 5, Funny

    Since when are Safari's ever "bug free"?!?

    --
    Authority questions you. Return the favor.
  3. Firefox? Safari? IE? by serviscope_minor · · Score: 5, Funny

    What about lynx, or better yet, telnet 80???

    Bonus points for running the javascript in your head.

    --
    SJW n. One who posts facts.
  4. Re:Review summary: "It's not the same as FireFox" by DogDude · · Score: 5, Informative

    No, that's not what he said. He said that Safari ignores most Windows conventions. That's bad.

    --
    I don't respond to AC's.
  5. Re:Oh really? by anethema · · Score: 5, Insightful

    Both firefox and opera are available to windows yet most people use internet explorer. See the parallel?

    --


    It's easier to fight for one's principles than to live up to them.
  6. Horrid UI by mattgreen · · Score: 5, Insightful

    It astounds me that Apple flips the bird to all of the Windows UI conventions for marketing purposes and nobody seems to care. Everything from their own anti-aliasing algorithm for text, their own custom widgets, to windows that you can only resize from the right corner. Of course, many legit Windows applications do the same thing, but it seems highly hypocritical of Apple to say, "you should stick to conventions when designing UIs" and then hardcode their own ideas in when developing on another platform.

    It is ridiculous how many vendors insist on ignoring platform conventions for no good reason whatsoever. Why does every application have to have a God complex and say, "I'm so great, I'll put shortcuts in your start menu, quick launch, two tray icons (including an autoupdater) and now I have a custom UI so I look special." Whatever happened to programs just doing their job in an unobtrusive manner?

    1. Re:Horrid UI by ip_vjl · · Score: 5, Insightful

      I agree it is out of place as a Windows desktop application.

      Though, if you look at it as the iPhone SDK instead, some of the choices make sense. You'd want to (for example) use the same anti-aliasing mechanism and widgets as the target device so that you know you're seeing things as they will look when deployed.

      I don't plan on using Safari as my primary browser, but for compatibility testing websites, the fact that it isn't using a different Windows-specific rendering style makes it valuable for that role.

    2. Re:Horrid UI by Doctor+Crumb · · Score: 5, Funny

      Funny, all of my apps are well behaved, and only put a single entry in the logic part of my application menu. Maybe your apt-get is broken?

    3. Re:Horrid UI by truthsearch · · Score: 5, Funny

      What conventions? "I'm so great, I'll put shortcuts in your start menu, quick launch, two tray icons (including an autoupdater) and now I have a custom UI so I look special." That's every Microsoft app. Microsoft doesn't follow their own UI guidelines on their own platform, so why should anyone else?

    4. Re:Horrid UI by Phroggy · · Score: 5, Interesting

      It astounds me that Apple flips the bird to all of the Windows UI conventions for marketing purposes and nobody seems to care. Everything from their own anti-aliasing algorithm for text, their own custom widgets, to windows that you can only resize from the right corner. Of course, many legit Windows applications do the same thing, but it seems highly hypocritical of Apple to say, "you should stick to conventions when designing UIs" and then hardcode their own ideas in when developing on another platform. You're obviously not a Mac user! You'd be far less astounded by this if you understood that Apple has a history of flipping the bird to all of the Mac UI conventions for marketing purposes. I'd say this dates back to about QuickTime 4. Eventually, Apple documented some of their own UI abuses, such as the arbitrary use of the brushed metal theme instead of the standard Aqua theme. It sounds like Leopard will have some convergence between new Mac UI guidelines and the actual UI of Apple's new apps, though, which will be good!
      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  7. I have a similar reaction to iTunes. by kmcrober · · Score: 5, Insightful

    While I love the iTunes Music Store service, the iTunes software is a dog. It's slow, choppy, resource-intensive, and rarely loads the iPod on the first try. (I'm happy to give Vista a portion of the blame, but only so much.) Even worse, when I transferred my library across computers I had to edit the XML file myself to preserve my ratings and playcounts, and an undocumented change in the way iTunes handles certain older MP3s meant that nearly 500 files were lost. Because iTunes didn't report the error, it took me days just to figure out which files were missing from the library, and I had to re-encode them because iTunes will neither load them or report any error with the files. I still don't know what the problem was, and Apple's help desk was no help at all. I wouldn't accept such poor performance and nonexistent error-reporting from shareware, much less a flagship product that's intended to sell me on their systems.

    I used to be on the bubble about switching; iTunes pushed me away from Apple instead of encouraging me to make the leap. I still use it, because the Music Store itself is perfect for my needs, but I'm not surprised to hear that Safari is a poor effort.

    If Apple wants to encourage people to switch, perhaps it should make some its better applications available, at least in a limited form. I love Dashboard and Expose (I think those are the right names), and simple commercial versions of those for the Windows environment might convince people to try an OS with better, smoother versions of those features built in.

  8. The reason Safari is on Windows... by daveschroeder · · Score: 5, Insightful

    ...isn't to entice people to buy a Mac.

    It's to act as a development vehicle for iPhone, since all third party iPhone apps will be rich Web 2.0/AJAX applications.

    On this topic, such applications can indeed have the look and feel of iPhone applications, and have access to all iPhone internal services, such as phone dialing, access to maps functionality, and any other iPhone services.

    This isn't just, "Oh, let's bring out Safari for Windows for the hell of it, and let people see how good of a browser it is, and maybe they'll buy a Mac!"

    This is the "SDK" for iPhone.

  9. Re:Safari, and Mac OS X, are better. by s4ck · · Score: 5, Funny
    Come October, Mac OS X will serve everyone with one price, one version, one install: one vision of simple 64-bit desktop goodness.

    one faith, one land, one volk, one fuhrer!! zeig heil!

    Does it come with a brown shirt?

  10. Re:Meh, Safari by TheRaven64 · · Score: 5, Insightful

    Safari is not based on Konqueror. Konqueror is a fairly generic application for running plugins. One plugin is KHTML, which is used for web browsing. WebKit, used by Safari, is based on KHTML.

    Apple evaluated Gecko. They even hired Dave Hyatt to lead the Safari team. If you're not familiar with Dave's other work he:

    • Worked at Netscape from 1997 to 2002,
    • Created Chimera, which was later renamed Camino.
    • Co-created Phoenix, which was later renamed Firefox.
    • Wrote the first specifications for XBL and XUL
    In spite of his obvious and heavy bias towards Gecko, he chose KHTML. That should tell you something about the quality of the Gecko codebase.
    --
    I am TheRaven on Soylent News
  11. Re:Review summary: "It's not the same as FireFox" by badasscat · · Score: 5, Interesting

    If the Windows conventions were good, I'd agree with you. However, anything is an improvement over Windows conventions.

    Come on; it's shocking as a Mac user to see all you Windows guys suddenly defending Safari now that it's available on your PC's. A lot of Mac users hate Safari. Many of us use Firefox.

    Safari on Mac doesn't follow Mac conventions either. It just received its first update in like a year, and it doesn't seem to have helped much. Safari:Mac = IE:Windows. We feel pretty much the same way about it.

    I use Safari on Mac only to test; that's about all it's good for, but its rendering engine always makes things look significantly different than any other browser so, like IE, as a designer you kind of just have to accept its quirks. I run Firefox as my primary browser on both Mac and PC.

    btw, I did try Safari on Windows. The first time I opened more than 10 tabs simultaneously, it froze. Yes, it's a beta, but a pretty unusable one if it fails at its basic core function.

  12. Missing the point by catmistake · · Score: 5, Insightful

    First of all... its a beta (so you better believe it has deficiencies!). Second of all, they didn't do it to give Windows users a taste of OS X, but to widen the developer base for iPhone web apps, and because Google pays Apple every time someone uses the Safari Google thingy.

  13. You are almost exactly wrong by Space+cowboy · · Score: 5, Informative

    Apple and MS have very different philosophical approaches for text rendering. Microsoft attempt to make the text as readable as possible on an LCD screen, to the detriment of the original font design. Apple preserve the font design to the detriment (for some people, I like it) of the readability.

    The main reason MS fonts look lighter is that Cleartype renders to pixel boundaries - if the font would naturally go over a pixel boundary when anti-aliased, Cleartype does not render that. The fonts end up looking "lighter" on screen because of it. Apple don't do that. As far as I know, It has nothing to do with colour and black & white.

    The upshot is that MS text appears lighter (they even designed fonts to match their rendering philosophy) than Apple text under most circumstances. It also means that the print output on a Mac looks very similar to the displayed output, whereas printing an MS document can make it look a lot "heavier" because the rendering on print is different from the rendering on display.

    As for 'proprietary', both rendering engines are 'proprietary'. I don't see why you call one that, and not the other.

    Simon

    --
    Physicists get Hadrons!
  14. Re:Review summary: "It's not the same as FireFox" by smenor · · Score: 5, Insightful

    He said that Safari ignores most Windows conventions. That's bad.

    I'm a Mac user and a huge fan of Apple's, but I completely agree that's bad.

    One of the most frustrating things about using Firefox in OS X is that it looks and feels horribly wrong because it ignors most Mac conventions*.

    What's good for the goose is good for the gander.

    I was prepared to call the article FUD before reading it... but then I noticed that it's Ars so I read it, and not only do the complaints seem valid, I don't even understand what Apple was thinking with some of the issues. For example, porting the OS X antialiasing over to Windows rather than using the native ClearType just seems weird (almost to the extent that I don't believe Ars Technica).

    *

    Yes, I know about Camino, but that doesn't diminish my point.

  15. Re:Review summary: "It's not the same as FireFox" by Zarel · · Score: 5, Informative

    Sounds much like every Java app. A lot of GTK+ apps. On Mac: every app not written by Apple or Adobe (all 3 of them).

    This is the reason why whenever people ask me what cross platform toolkit they should use I say: none. Write a GUI for each platform you want to support and use a common backend.. that way you are more likely to write a GUI that is suitable for the platform.

    Of course, when they insist, I suggest they use Qt. The problem isn't that it doesn't follow UI conventions - Windows users are used to that; every company and their mother design their own UI. The problem is that it brings its UI conventions outside to the window border/window decorations. Specifically:
    • Can't resize by dragging window edge - This is the one the article mentioned, and it's the worst. No other Windows app I've used, not even the particularly egregious, suffer from this problem (excluding the ones that aren't meant to be resized at all).
    • Doesn't understand how to maximize - In Windows, maximizing means more than resizing the window so the edges touch the screen edges. 1. It means the window can't be resized, so don't show any resize handles. 2. It means the window takes up the whole screen, excluding the taskbar. 3. It means the window is the only window on screen. Open and maximize Firefox, then open and maximize Safari. If you click on the top right corner of the screen, you would expect Safari to close. But not only does Safari not close, Firefox closes. (Trillian is the only other Windows app I've used that suffers from the same problem, and is the reason why I now set Firefox to confirm before closing.)
    • Doesn't understand the taskbar - In Windows, when I click on a window's taskbar button, I expect it to minimize if it isn't already minimized. When I right-click on the taskbar button, I expect to be able to minimize, restore, and maximize, depending on which state it's in.
    • Doesn't act like a window - If I press WLK+M, I expect all windows to minimize, not all windows except Safari. If I use the taskbar to cascade or tile windows, I expect every window to cascade or tile, not every window except Safari. In short, I expect Safari's window to behave like a window.
    These are problems no other Windows application suffers from except Safari (with the exception of Trillian). Even the worst GTK apps suffer from is OK/Cancel button order switching.
    --
    Want a high quality FOSS RTS game? Try Warzone 2100!