Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jon Rose on Nov 17, 2009
Adobe Systems has announced the availability of beta versions of Flash Player 10.1 and AIR 2.0, which can be downloaded from the Adobe Labs site.
Flash Player 10.1
The minor increment in the version number, from the currently available Flash Player 10, may be misleading, as the release signifies Adobe’s first major step in their push to bring the ubiquity the Flash platform enjoys on the desktop to smart phones, netbooks, and other devices. In the time since the Open Screen project was announced in 2008, Adobe has shifted much of their focus around the Flash Player to making improvements that will make the runtime usable on mobile platforms. Adobe’s David Wadhwani shared the following on the release:
With the beta availability of Adobe AIR 2 and Flash Player 10.1 today, we are taking an important step toward realizing the Open Screen Project vision to enable rich Internet experiences across any device, anywhere.
This beta is only available for PC’s, with release to come in the future that will bring version 10.1 of the player to numerous mobile devices and netbooks. Much of the work to make the runtime viable on mobile devices and netbooks has been around improving both memory consumption and CPU usage.
As we move into technologies with very limited memory and processing resources, Flash Player had to become as optimized as possible to get out of the way of your content. We reduced its memory allocations and found innovative ways of sharing memory and taking advantage of specialized hardware whenever possible—all with the goal of giving your content the most memory and processor availability we can. Your content may have been optimized with a desktop computer in mind, but we will do all we can to overcome the technology gap and run your app as close to desktop quality as we can.
In addition to improving the overall footprint of the player, a number of other updates have been included in the release:
Please refer to Justin Everett-Church’s article on the Adobe Developer Center for more detailed information on the Flash Player 10.1 features.
AIR 2.0
In addition to all of the new Flash Player features that are available on the desktop within the AIR runtime, the AIR 2.0 release includes a number of updates for those developing desktop applications. Adobe’s Rob Christensen provides an overview of what’s new in AIR 2.0:
As a team, one of our stated goals for AIR 2 from the beginning was to add capabilities to the runtime that would enable new classes of applications to be built that were simply not possible with AIR 1.
...
As the definition of AIR 2 evolved, it became clear that we would focus our efforts on the following themes: providing deeper integration with the operating system, making developers more productive, and improving performance.
AIR 2.0 major feature updates include:
Please refer to Rob Christensen’s article on the Adobe Developer Center for more detailed information on the new AIR 2.0 features.
I can't find a link for the AIR 2.0 Beta download...Can anyone help?
Thanks!
Thanks, found it...at labs.adobe.com/downloads/air2.html
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
2 comments
Watch Thread Reply