Best of this Week Summary 02 March - 08 March 2009

• The UI teamlead of Google's Chrome browser explained at a presentation why they decided to build Chrome. Basically because all the existing browsers suck :-)
  


• A memory and performance comparison between Seam+JSF and Wicket. Wicket wins both. Also check the comments for useful feedback. Possible reasons for the differences in performance are: JSF performs much more expression evaluation and the JSF lifecycle is much more complex.
  


• The Open Group has released version 9 of The Open Group Architecture Framework (TOGAF) for enterprise architectures. TOGAF is often combined with ArchiMate for modelling. Most important addition to version 8 is the content framework which describes what an architecture exists of. Here's some feedback from actual users on TOGAF 9.
  


• Talking about standards, the OASIS committee has updated a bunch of webservices specifications/standards.
  


• A nice post on how to write a Javascript client that sites can use to access your REST API. Biggest challenges that had to be solved were:
  

  1. Browser same-origin restrictions on XMLHttpRequests (XHRs) and inter-window/frame access
     
  
  
  2. The lack of wide browser support for HTML 5-style message passing between windows.

• Java Enterprise Edition 6 (Java EE 6) Specification (JSR 316) is getting there...
  

Best of this Week Summary 12 November - 18 November 2007

• Ten tools to manage your SOA in the area of governance, quality and management. For each of the tools it shortly describes what the tool does does, who's behind it and which companies are using it.
  


• Seven good tips and overview on how to make your Javascript unobtrusive.
  


• Jilles van Gurp (who works at Nokia) describes his initial impressions on Google's Android SDK, a platform aimed at mobile devices, released earlier this week. Main thing to note is that Google has built their own JVM Dalvik and it is another Java spin-off; it is not JME. Here's why this is not such a good thing. And here's some points why it should be better than JME. Note also that Nokia is not (yet?) part of the Open Handset Alliance.
  
  


• Here's a Javascript library that "solves" the same-origin-policy problem I mentioned in a previous post on OpenSocial by using _IG_FetchContent, which goes via a proxy server. Check also his other 2 posts (First and Second step), providing a higher level wrapper library (API) on top of OpenSocial.