By BoLOBOOLNE payday loans

Safari for Windows

So Apple is releasing the Safari browser for Windows.  My first reaction is "great, just what we need — another minority browser."  It’s a funny move for Apple because IE will probably remain the #1 browser for quite a while just because of inertia, even as Firefox gains shares based on markedly superior features.  So realistically the best Apple can hope for is #3, which really isn’t their style.  Their claims about speed just aren’t going to win over users because application performance just isn’t that important for browsers on full-sized computers.  On small computers with limited CPU people generally don’t have a choice of browsers.  That could win over embedded platform developers if Apple were to allow the source to be ported (unlikely IMHO).

Safari does have some innovative UI features which will win them some
fans.  Without IP protection I’m guessing it won’t take long for the
Mozilla kids to replicate them.  (If there’s one thing open source is
good at it’s building a project to match somebody else’s spec.)  I
really doubt Apple will be able to keep innovating useful features fast
enough to keep a meaningful lead for long.

The real reason they’re doing this is of course to make it a more attractive platform for people to write applications for the iPhone.  It’s a close analogy to how Microsoft supported IE for Mac — the only reason is to have a reasonable cross platform story.  This is another sign that Apple’s betting big on the iPhone.  The fact that it won’t be easy to text while driving will limit its usefulness for some people.  It’s a symptom of the phenomenon that even with a great touch-screen like the iPhone has, generic UI’s aren’t as good as single-purpose UI’s.

Attracting web developers is
really what Apple needs to do.  Listening to my coworkers, they’ve got an uphill battle ahead of them.  Safari claims to be based on standards, but I hear it’s a hassle to get things to work properly in it.  Right now, the subtle HTML/CSS rendering differences aren’t nearly as important as differences in javascript behavior.  For a long time Safari has been missing some a few key XML parsing APIs for AJAX.  In the near future, the key differentiator for browsers is going to be the availability of good libraries for off-line web applications, like Google Gears.  Unless they talk Google into release Gears for Safari, I predict this isn’t going to go very well for them.  I hope we don’t see too much industry fragmentation here.

  1. Jeff at www.thenewsroom.com says:

    I totally agree, and so does AP: http://thenewsroom.com/details/422936?c_id=wom-bc-js

  1. There are no trackbacks for this post yet.