Tech Team Lead News: chrome

Showing posts with label chrome. Show all posts

Sunday, March 8, 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...

Lots of OpenID news this week: Microsoft Live ID will be an OpenID provider. It is still in a testing phase; you can already try it out. Google is also going to be an OpenID provider, including the use of OAuth. But that looks less promising when looking carefully: the implementation is not completely following the OpenID standards! See step 3 and 4 in the image below.

A clarification on why Google has done this can be found here. Basically, two reasons:
1. this way users can use their Gmail accounts instead of the normally required URLs. But a URL does exist in the form of 'https://www.google.com/accounts/o8/id'.
2. Google doesn't allow OpenID for users at sign-in, because its federated login would break many of their rich-client applications. Google is working on this one.

Whitepaper on how the JTeam company has implemented Continous Integration. Their complete list of CI tools is described; handy when you're looking for inspiration.

Things to think about when considering Maven as your build tool (different angle on the post :-)

Interesting posts from the Google Chrome team on the decisions they made creating the browser.

A list of the 10 worst scalability practices/anti-patterns for large distributed systems. The areas covered are: the golden hammer: use of only 1 technology, resource abuse, big ball of mud: bad versioning/deployment management, everything or something: packaging of the application, forgetting to check the time (did you know that only just recently, since JDK 1.5, you can set timeout on reads on HTTPURLConnection? And that DNS lookups in Java are cached for the lifetime of the JVM unless configured differently?), the hero pattern: one operational "do it all", not automating deployment, build etc, and finally: monitoring of the system.

In case you lived under a rock the last week without Internet access :-), Google introduced its browser: Chrome.
A couple of interesting things from posts around The Net: Chrome does a better job on the ACID test than the latest Firefox 3 build and IE 7.
The first performances tests show that Chrome's performance is outperforming all the current browsers!
Mozilla countered this with another test using their new javascript engine TraceMonkey, which should be released by the end of the year in Firefox 3.1. And this is the current standing in browser marketshare.
Quite a big surprise is that it is currently only available for Windows. Clearly Google is going for marketshare by addressing the users of the most used operating system... And finally, below is an overview how Chrome got its logo (via neatorama, with custom edit):