Slashdot Mirror


Is Safari the New Internet Explorer?

An anonymous reader writes: Software developer Nolan Lawson says Apple's Safari has taken the place of Microsoft's Internet Explorer as the major browser that lags behind all the others. This comes shortly after the Edge Conference, where major players in web technologies got together to discuss the state of the industry and what's ahead. Lawson says Mozilla, Google, Opera, and Microsoft were all in attendance and willing to talk — but not Apple.

"It's hard to get insight into why Apple is behaving this way. They never send anyone to web conferences, their Surfin' Safari blog is a shadow of its former self, and nobody knows what the next version of Safari will contain until that year's WWDC. In a sense, Apple is like Santa Claus, descending yearly to give us some much-anticipated presents, with no forewarning about which of our wishes he'll grant this year. And frankly, the presents have been getting smaller and smaller lately."

He argues, "At this point, we in the web community need to come to terms with the fact that Safari has become the new IE. Microsoft is repentant these days, Google is pushing the web as far as it can go, and Mozilla is still being Mozilla. Apple is really the one singer in that barbershop quartet hitting all the sour notes, and it's time we start talking about it openly instead of tiptoeing around it like we're going to hurt somebody's feelings."

9 of 311 comments (clear)

  1. Re:People still use Safari? by carlhaagen · · Score: 3, Informative

    Yes.

  2. Re:This is a big troll by Anonymous Coward · · Score: 4, Informative

    Safari does not do either of these things.

    Ah the RDF.

    1. There is plenty of safari-specific CSS that renders improperly in competitors' browsers (the same is true of IE, Chrome and Firefox as well). Back in the late 90s/early 00s the problem was you do things the IE way or the Netscape way, many of which were non-standard. Nowadays browsers still introduce their own extensions and ways of doing things with different quirks hence the safari/webkit/chrome/ie/etc CSS prefixes.

    2. Here you will find pages and pages disproving you.

    Note: All the browsers have such problems, not just Safari. Just calling you out on your false idea that Safari doesn't suffer the problems of other browsers. The point of this article is that Safari is becoming the new IE in the sense that with respect to industry collaboration they are behaving like Microsoft did with early IE. Try not to extrapolate beyond that.

  3. Yes, people still use iOS by tepples · · Score: 5, Informative

    Just because you no longer use Apple's iOS doesn't mean millions of other people don't still use iOS. There are two kinds of browsers on iOS: browsers that run remotely and behave akin to Remote Desktop, such as Opera Mini, and browsers that wrap the system's UIWebView or WKWebView control, such as Safari. The App Store Review Guidelines forbid third-party web engines that run on an iOS device. This means the vast majority of browsers for iOS are essentially window dressing around Safari.

  4. Re:New internet explorer by tepples · · Score: 2, Informative

    If only enough people that mattered used Safari.

    You mean other than CxOs and VPs that carry an iPhone and/or iPad?

  5. Re:Why all the Safari/Apple hate ?... by dazol · · Score: 4, Informative

    As a 42 year old system engineer (*nix) I can say your inexperience is showing. There hasn't been a company I've worked for who didn't have a plethora of Macs in the hands of the developers, SysAdmins *and* managers.

    Most of our linux admins? Macs.

    Half our Windows admins? Macs.

    1/4 of our developers? Macs.

    Went to a couple Puppet conferences. Most of the laptops? Macs.

    etc, etc, etc.

    The rest of your comment is pure applesauce.

  6. Re:I think Apple's glory days are over by Known+Nutter · · Score: 5, Informative

    digital and carts are different.

    When you're describing vendor lock-in, I fail to see how the comparison is not relevant.

    Does google make me use google play to load an MP3? no but apple makes you use iTunes

    They do? Are you high? I just took one of the tracks from that U2 album Apple pushed. Track 6, Volcano. I took that track, an m4a, copied over to a Windows box, and played it in VLC. VLC runs on OS X along with a host of other MP3/media players. So, wtf were you saying??

    can i use chrome in IOS??? No!... (not really anyway)

    So no...fine, user lock in without Chrome. Give me a break.

    can I keep ticking off things I can do in other OS's that I cant do in osX or iOS?? yes

    You better keep trying, because your first two sucked ass.

    --
    Beware of the Leopard.
  7. It's their business model. by sbaker · · Score: 3, Informative

    When you expect to get most of your revenue from selling apps in the iStore - it's essential that people are unable to get apps for free via fancy web pages.

    Hence, iPhone doesn't support WebGL for doing fancy 3D graphics on a web page - if it did, people would write cool games in HTML/JavaScript/WebGL and monetize them directly without having Apple take 30% of the revenue and "approve" their product.

    Is this because Apple can't support WebGL? Hell no! The browser actually DOES contain code for WebGL, but it's disabled...UNLESS your web site signs up to display Apple-provided advertising banners...in which case, WebGL works great!

    Safari uses the exact same core rending software ("WebKit") as Chrome - so it can trivially support everything that Chrome supports - it's really just a matter of Apple deciding to deliberately cripple the browser to prevent people from providing apps for free.

    --
    www.sjbaker.org
    1. Re:It's their business model. by Anubis+IV · · Score: 5, Informative

      How does a post that gets almost all of its facts wrong get modded up as Insightful? You started on a provably faulty premise, backed it up with inaccurate statements regarding WebGL, and then closed it out by saying something that I'd have hoped most of us here would trivially recognize as incorrect.

      When you expect to get most of your revenue from selling apps in the iStore

      Apple announced at the start of the year that they've paid out $25B to developers over the life of the App Store. Do some quick math, and that means that Apple is averaging $0.45B in revenue each quarter from the App Store, which would put it at <1% of their quarterly revenue (e.g. Apple posted $60B in revenue in their latest, post-Christmas quarter).

      Which is to say, your basic premise here is that Apple is intentionally crippling the product that makes up 60% of their revenue (iOS hardware) in order to bolster the revenue in a segment that accounts for less than 1% of their revenue (App Store downloads). Seriously? Apple's main business isn't selling apps; it's selling selling devices that run apps, and you may even recall that back when the iPhone launched in 2007, the "apps" it supported were web apps, not native apps.

      iPhone doesn't support WebGL for doing fancy 3D graphics on a web page

      Could've fooled me. iOS 8 has been out for nearly a year at this point, and has had WebGL support from the beginning without any of the weird requirements you're talking about.

      The browser actually DOES contain code for WebGL, but it's disabled...UNLESS your web site signs up to display Apple-provided advertising banners

      A) You're confused. You're talking about iAds (and I'll discuss why I know you are in a sec), but the iAd advertising network only operates in iOS apps, not on websites. Sites can't sign up to it.

      B) It's not disabled. See above. WebGL support was available as an experimental feature in iOS 7, and as a standard feature in iOS8. No ads or other funny business required.

      The reason you're confused is because, technically speaking, iOS did have support for WebGL as far back as iOS 4.2, but it was only available to iAd developers. By that, I don't mean people who agreed to put iAds in their app. I mean people who were actually making the iAds themselves, since iAds are basically just mini webpages that display an ad.

      If that seems a bit weird at first glance, recall that WebGL was a resource-intensive feature on the devices of that day, and Apple has a history of restricting the scope or operation of resource-intensive features until the implementations or device capabilities improve (see: background processing, native apps on Apple Watch, etc.), so it made sense at the time why WebGL was restricted to iAds, since they were designed to only be on the screen for short periods of time yet could stand to gain the most from such a feature.

      The only sense in which what you said is correct is that for a few years the only people who were able to make use of WebGL on iOS were the ones making the ads, but it was never a feature that web developers had to make a Faustian pact with Apple to use. It simply wasn't available to them.

      Safari uses the exact same core rending software ("WebKit") as Chrome - so it can trivially support everything that Chrome supports

      They haven't both used "WebKit" since Google forked WebKit to create Blink over two years ago, but even before that, they weren't even running "the exact same core rendering software" for the last several years back when they were both running "WebKit".

      Google and Apple have had divergent multi-process architectures for quite some time. Google built

  8. Re:Safari was late in implementing some web APIs by Dog-Cow · · Score: 3, Informative

    Your reasoning is way off. Apple does exactly what you claim they didn't want to do all the time. Siri is not supported on some models that run iOS 7. The new multi-tasking in iOS 9 (multiple on-screen apps) is only supported on newer iPads, and not the iPhone at all, not even the 6+. So basically, you're so completely wrong it's not even funny.