"The more you reason the less you create." : Mitch Kapor exits the Chandler project. One suspects the analysis will center on Kapor, paid-for OSS, and "process", CNET's analysis being typical: "The best communal open-source projects are run like Mozilla (strong core development team with easy pluggability from the outside)," . The real question to ask is whether building a desktop PIM makes sense anymore; personally I doubt it.

Java APIs aren't data silo busters. Adrian Sutton calls Atom the new JCR: "along came Atom which is all about remote access and manipulation of data and missing probably 90% of the functionality that JCR offers. It really isn't a competitor to JCR at all and yet it's doing more to break down content silos than JCR ever has. Atom support isn't just being added to the marketing materials, it's actually shipping". In a similar vein, compare the Java Content Repository's (JSR170) it's all nodes and objects approach to the IBM Jazz approach: "So our proposition is that rather than producing large, monolithic models and closed tools we develop with a much more fine-grained approach and move from a file-system approach to a repository approach. It is also important that the repository should need to know as little as possible about the resource types".

Down to the wire. Forbes reports on the FCC spectrum auction: "New and better wireless services will arise in the future, but not necessarily because telcos want them. Google and others are pushing telcos--which move slowly and generally operate closed networks as a form of quality control--to open their networks to outside hardware and software developers, and thus, spur innovation and competition.". The mobile landscape is the next great tech battlefield - 3B subscribers can't be wrong .It might help explain whether Android has a business model, because one thing is for sure, Android is strategic to Google, not a 20% project that got lucky -  "We have our own APIs [and] a better flavor of Java," Dianne See Morrison: "Telcos are once again painted as the lumbering, wary giants who are being dragged kicking and screaming toward innovation." Painted is right, the telcos seem to understand the dynamics well enough.

Configuration is code. Sean McGrath gently reminds us that configuration sometimes can better done using code. Other warning signs might include - XML starts nesting deeply; there's an attributes pile on;  jakarta commons configuration looks like radical simplification. For Java folks looking to kick the XML/.properties habit, Jython and Javascript are decent options.