I'm not a indie Mac developer but I buy a lot of their wares and it has been a major factor making my Mac experience more pleasant than any other previously had. And as some of them, I was disappointed about them not getting the iPhone SDK they all wanted. It would spur a flurry of applications for sure. But bottom line: the iPhone is a very restricted platform. Low memory, battery operated, and very different user interaction than your keyboard/mouse combo.
There. I did a iPhone post. I'm cool. Not.
Great read to start the day. Don't you just love hyped-up releases?
First, let me just say, in case you are new here, that my current main work computer is a Macbook Pro 17", 1st generation. Today I came across a comparison between a MacBook Pro 17" and a Asus laptop, with a big title like "I'll prove to you that MacBook Pro cost $500 more than PC". To be blunt: who the fuck cares? You should buy the best tool for the job you are planning on doing.
As with all Steve jobs keynotes, everything is great, all Apple apps are the best of the world. The part about Safari 3 was no exception, and he mentioned that Safari is now the speed champion. As always, speed is subjective and some times difficult to test, but I remembered the ExtJs library speed tests for DOM matching. The cool part of these tests is that they do about 28 tests with several different JS libraries.
To me the most unexpected news out of WWDC 07 was Safari available on Windows. At first, all I could think was: WTF?? Why waste precious engineering resources on this?? But after the announcement of the "iPhone SDK", it all makes sense: they need a Webkit-capable browser available on all platforms to make it easier to test future "iPhone Apps". That small detail aside, Safari3 is working ok for me with the latest Mac OS X 10.
Yesterday, while looking over to the Google Gears (GG) stuff, I talked with Celso about this and that I was pretty excited with the possibilities it provides. He was not impressed and later he told us why. I'm going to pick on his arguments for a while and then, in a followin post, tell you why I like Google Gears and where I think I can use it today. I don't think it is the 8th wonder of the world, but I think it is a very good step in a good direction.
As I said on my previous post, I'm looking over the documentation of the Google Gears (GG) stuff. I read it all yesterday at night, and though about it. The things I like about GG are pretty simple. The first one is that you can write your applications to take advantage of it if present, but work the same if not. Its not a all-or-nothing approach, its more of a progressive enhancement thing.
Google announced Google Gears, a browser extension that allows web applications to have a offline-mode available. Right now, most recent browsers are supported with two omissions: Safari (on which the team is working on - my bet is expect this with Leopard and the new, more powerful, WebKitaccording to the developer (7:00), you can build a Safari plugin from the SVN code but another post mentions that it will only works with the nightly builds of WebKit), and Opera (which is not even mentioned).
Nothing more to say, really...