« Open Flex links, 2 | Main | "Desktop v browser" distinction »
April 26, 2007
Open Flex links, 3
Open Flex links, 3: In the extended entry, an annotated blog trawl of commentary where I learn something new. Last night's catch here; overnight links caught this morning here. I'll be updating this post throughout the afternoon. Links are in order I find them, most recent at the bottom.
NetCrucible.com doesn't credit an author or have an "About" page... I got here through Techmeme... dismisses the evolution: "From what I can tell, Adobe looks to be trying to make some news out of thin air right now. As Ted observes, it's a promise to open up some really non-essential parts of the platform. This can't be too exciting to Google or Mozilla, so I assume it's just an attempt to generate a bit of incremental goodwill." (Ah, a WhoIs search shows that this is the blog of Joshua Allen of Microsoft. Not disclosing affiliation logically leads to suspicions of other sockpuppetry and skullduggery, boyo....)
Jeff Whatcott has a reply to Dana Blankenhorn's "sign of desperation" piece: "We're open sourcing Flex because we are on roll. We've hit a critical mass of adoption, technology maturity, and marketplace maturity, in which an open source project can really take off in a meaningful way. Customers are succeeding, revenue is growing, our community active and intimate, and people are coming to us with great ideas on how to make the technology even better. I'd be happy to talk to you live if you want to discuss it further...."
Grant Robertson has two paragraphs on the story at DownloadSquad, but I particularly like his title: "Adobe open-sources Flex, developers cheer"... puts me in an Irving Berlin kinda mood.... ;-)
Mike Chambers, on the Apollo team: "We haven't announced any plans at this time to open source the Apollo SDK. We are still in our alpha / beta development stage, and thus we don't even know for sure what all will be within the SDK. However, once we have a better picture of what the final SDK will include, then I don't think it is unreasonable to expect that the Apollo SDK, or parts of it, will follow the same path of the Flex SDK, especially since they are so tightly integrated."
Matt Woodward and Keith Peters are a little annoyed with the buggy commentary in much of the proprietary press. FlashForward blog issues a dare to melt the Internet, and I'm game for that.... ;-)
Mark Piller discusses possible futures with WebORB.
The above came from Techmeme and MXNA... let me post these, come back and do some searching and browsing....
Jihad Dannawi, of Microsoft/France, had the first post in the MSDN aggregator... I think he's saying that Flex was little more capable than Dreamweaver and was soon due to die of fright from Silverlight, but that it would free up Adobe engineering for Apollo (machine translation). Royale avec fromage right back atcha, baby!
Valveblog (Matti Djateu?) recaps the core info which many of today's objecting pundits haven't heard: "Now people of course start going 'c'mon, the only thing you haven't open sources in the Flash Platform is the FlashPlayer (apart from the AS3 engine), how about opening it up?'. Dare not wish things you really don't want to see, say I. It's ok to let everyone contribute to the Flex SDK, and have millions of builds flying in each direction, since in the end, a flaw build only crashes one single application. But imagine a community driven FlashPlayer out there. New releases and branches every week. Some group would add 3D Hardware acceleration immediately, others would work on MOD-player support, and both would be distributed and not compatible and we would loose the most important aspect of Flash -- ubiquity." Thanks for the reminder!
Main Digg discussion has received over 1000 recommendations now.
The Serverside has 20 comments so far. Much of these are about sussing out which source code is available, etc. They've been burnt by Microsoft and Mono. James Ward is filling in the informational gaps there.
Par Aggelos has the first of a three-part analysis, this part focusing on recent history from the perspective an MTASC user.
... I'm starting to fade... the search engines have lots of reruns and copied text now, and the entries are starting to blur together... let me close out some windows here and take a break....
Andrew Shebanow of Adobe has original text, putting context from the past several months around the announcement.
Ammon Lauritzen is a little annoyed with some of the uninformed noise out there, but then goes through the compiler/debugger distinctions and draws a steely gaze on the DataGrid component....
No name at psyked.co.uk, and it seems like original text but with familiar info... closes with a nice line about the shovel-selling business.
Cote of Redmonk has a few screens of text on varied related topics, but I'm not sure I can pull out the main idea(s) by this point.
Igor Costa offers a perspective from Brazil.
Alan Lewis has related experience from publishing some of the eBay APIs.
Josh Sager has a "scream it from the mountaintops" lede, and notes that he feels like he can change the course of technology here.
This is the post that made me tired... has more ads than words of original content... we may be at the point of diminishing returns for blogsearch, at least until this initial wave of robots dies down and we get individuals posting thoughts again.
I'll do another pass this evening.
One more before I perambulate... Ryan Paul at Ars Technica covers it, and that site usually draws interesting discussions.
Posted by JohnDowdell at April 26, 2007 12:04 PM
Trackback Pings
TrackBack URL for this entry:
http://weblogs.macromedia.com/mtadmin/mt-tb.cgi/8662
Comments
> Not disclosing affiliation logically leads to
> suspicions of other sockpuppetry and
> skullduggery, boyo....)
Dude, the post was categorized under "Life at Microsoft", and the top right link (the most prominent possible position) of the blog has always disclosed my affiliation. I have been blogging from MSFT since 1999 and have never hidden the fact.
Posted by: Joshua Allen [msft] at April 26, 2007 02:16 PM
I saw a category titled "Life at Microsoft", which led me to wonder and then search for who wrote it and what their affiliation might be.
When anyone can alight on any page at any time, and when you speak of issues relating to where you get your paycheck, then it's a reasonable custom to disclose (a) your name and (b) your affiliation.
Microsoft has a definite history of bad faith here (search term "barkto incident", eg), and recently we've been educating some of your more trollish cohorts on just why they should put that little "/ms" at the end of their frequent screeds.
jd/adobe
Posted by: John Dowdell at April 26, 2007 03:01 PM
JD: No hard feelings. The "about" link has *always* displayed my name and affiliation, for 7 years. And even if you couldn't find the "about" link, a quick google on my name or the blog's name would have revealed that I have been associated with MSFT as a blogger since forever. I have *never* been accused of hiding my employment (and I always add the [msft] in comments -- I could write a book about best practices for disclosure, and you can read about me in Shel and Scoble's book if you want).
[jd sez: True, and no slight intended, Joshua. I've read your blog before, but could not link it to a name or person from the interface alone... in my searching I had jumped back to an index page, but it looks like I missed the "About" after that step, and went to WHOIS instead to refresh my memory. If you drink beer, then I've got the next pint, 'kay?]
Posted by: Joshua Allen [msft] at April 26, 2007 03:34 PM