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 Scott Delap on Oct 11, 2006
In fact, we have been tuned into this release and making Java work on it since it was named after a breed of cattle. Between regular calls with Microsoft, interaction with their engineers when problems or questions arose, and regular testing and engineering during Vista's development, we have been building a rock-solid release of Java for Vista.
Chet does acknowledge that older versions of Java may have issues on Vista. However this is to be expected with a major OS change:
Vista is not just XP++; there are fundamentally new things about the system that makes older software break. Is all software broken? Probably not. But the more of the system an application uses, the more likely it is to run into issues where the system has changed, and need to react to those issues. In our case, Java is not just a simple win32 GUI application; it is a runtime platform with deep rooted needs in the operating system, the networking stack, the security model, the graphics system, ... if any of these change significantly, then we need to change our software in reaction. And in the case of Vista, it has been an ongoing process of learning, testing, debugging, submitting bugs against Microsoft, fixing our bugs, re-testing, .... And since Vista has been a moving platform during the Java SE 6 development process, we've been in this development cycle continually with every new drop of Vista.
Java 6 will be the preferred version of Java for Vista. However, many Vista fixes have been backported to Java 5 with work continuing that will be included in a update slated to be released around January of 2007. Sun also plans to ship a Vista-enabled update to Java 1.4.2 after the Java 5 update.
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
18 agile and lean practices for effective software development governance
Getting Started with Stratos - an Open Source Cloud Platform
maybe its the image, but i dont see characters rendered properly on the screen
It's the image: the version above is not the original size, and the text didn't fare well in the scaling operation. Click on the image to see the original screenshot.
The original image's text may also look distorted, depending on your display; it was captured on an LCD screen and the text is therefore rendered with our LCD text anti-aliasing (new in Java SE 6). If your display is similar to the display it was captured on, it should look fine, but if your display's characterstics are different (like if you are viewing it on a CRT, not an LCD display), you may notice color fringing artifacts in the image that would not be there if you were running the application locally on your display.
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