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 Coach Wei & Dionysios Synodinos on Jul 04, 2008
An industry wishlist for future browsers has been collected and developed by OpenAjax Alliance. Using wiki as an open collaboration tool and with contributions from many people in the industry, the feature list now lists 37 separate feature requests, covering a wide range of technology areas, such as security, Comet, multimedia, CSS, interactivity, and performance. The goal is to inform the browser vendors about what the Ajax developer community feels are most important for the next round of browsers (i.e., FF4, IE9, Safari4, and Opera10) and to provide supplemental details relative to the feature requests.
The current feature request list is:
Security features
Client-server communications features
HTML5/W3C features
CSS features
Rendering/interaction/event handling features
Performance features
JavaScript features
Other features
OpenAjax Alliance is calling for everyone to vote for his/her favorite features. As befits an AJAX organization, voting is done using AJAX callbacks so that the votes are recorded asynchronously in the background:
The alliance also strongly encourages people to comment on the wiki pages for each of the existing features and to add any important new features that are not yet on the list.
This voting is open to anyone, including OpenAjax Alliance members and non-members.
I may sound like a Rebel but the fact is these words are coming from experience of facing useless Browser specific ways of doing things (better say fixing issues).
If you take a count of the number of people trying to fix the same x/html code with some java script and dhtml to behave same on all the major browser, you will get almost 100% of all the web developers in this count.
In fact more than any thing addressing this issue must be given highest priority, Enough of customizing the same code for various browsers, first of all this should never be a developers or testers concern, I have seen my own friends installing 3-4 browsers to check if the behavior of the same page is same on all the browsers on not! Some times that effort is more expensive then development it self!!
In my view there are few items which might be very useful.
- Support for native JSON parsing mechanism , seems to be a good thing. First thing is JSON is very popular so having parser will enable easy integration.
- Offline support is also a cool feature , because that will help Ajax developer a lot
- Xpath support
blogs.deepal.org
Not sure if this functionality already exists or not but can there be way to notify the user as and when a web page is updated? Example is a tutorial on a technical topic, when a new version of the framework/product is released and the tutorial is updated I would like to be notified.
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.
3 comments
Watch Thread Reply