JD on EP

Feels to me it's tied to the iphone which has a complete safari stack on it. If you want your site on the iphone make sure it works with safari, if your on a pc here is a copy of safari for your platform to build and test against. Itunes went cross platform to push ipod sales, maybe safari 3 has some hooks for iphone when synced to the pc etc. -ethan

I got a kick out of this line in the press release: "WWDC 2007, SAN FRANCISCO - June 11, 2007 - Apple today announced that its revolutionary iPhone will run applications created with Web 2.0 Internet standards when it begins shipping on June 29." I guess that's what comes after "web standards", "web 2.0 standards"... but shouldn't it be "web standards 2.0"? or maybe... oh, forget it, I won't go there.... ;-)

Similar malapropism in the New York Times account, although this was an indirect quotation rather than a direct statement by Apple: "Mr. Jobs said that applications that are written to Internet standards such as AJAX and designed to work with Web browsers would work from the first day the iPhone is available."

"AJAX" is a marketing term, and the operational element is the formerly-"proprietary" XmlHttpRequest from Microsoft... there's been talking about standardizing it (now that it's been deployed for ten years!) but the only way that "Internet standards" and "AJAX" can be in the same sentence is if we're talking about de-facto standards.

Anyway, these usages of "web 2.0 standards" and the like make me wonder just how thoroughly they've thought through their messaging... pieces still don't seem to sit together right, to me....

XHR is beings standardized (not just "talked about" here).

[jd sez: True, *now* it's going through the formal process. MS did XHR "proprietary" in the late 90s, and it's only the last 3 years other people have cared. It's almost like it's being blessed now...?]

And as I tried to say after posting the link, I agree the motive behind a Windows push is still unclear, though I guess I agree with the person who suggested all web developers can test for the iPhone now. Hey, 3 high-quality browsers now available for Windows. And also, Internet Explorer ;) Choice is good...

Given that Adobe is using WebKit in AIR, that 'AJAX'/XHR and the concepts of openness (licenses/community) and interoperability (Google Gears, Tamarin...) are part of Adobe's dev story, I didn't expect such a 'cool' response... unless I'm misreading.

One view would have Adobe benefiting; wider WebKit support cuts-both-ways, with an 'app' able to run on mobiles (iPhone/Nokia), desktop browsers, as an AIR application, embedded WebKit apps, and of course Widget's (OS X, Google.) That seems to play into the 'AIR story', and if it's really the most compelling solution, it's accessibility to Web(Kit) developers is a good thing.

IMHO WinSafari is clearly not targeting Firefox users, it's aimed at IE users, and any success increasing market-share should increase the proportion of 'standards compliant' browsers, further reducing the viability of targeting just IE... or Silverlight in the future, maybe. : )

...but then maybe I've misunderstood what you're trying to do with AIR, Flex, Spry, CS3 etc.

Not to be harsh,but the reason's pretty obvious...the Iphone and the "API." http://thenewsroom.com/details/394435?c_id=wom-bc-js

[jd sez: Looks like spam... the teaser to reveals no significant original content.]