"Web apps are a good solution some of the time (except for that little detail called IE!)."

This statement makes very little sense. You say that you can't use web apps because you would require client have a specific app (chrome) on their machine, but then you say the solution is that they must have a different specific app on their machine. I would re-write that or remove it.

Simple sample app would be great for the next post.

While interesting, I think the headline is a bit hyperbolic.

The Chromium project doesn't build on many platforms, and the build system they use for it is minimally documented.

While individual bits of code might be reusable on other platforms, I'd be hesitant to base any project I create on Google's codebase given the lack of portability and their reliance on arcane buildsystems.

I've also used Chromium libraries for cross-platform development in the manner you have suggested. What you might want to address is how you handle deficiencies in the base libraries --- how much do you have to rewrite when you see that the base implementations, which are fine for Chromium, don't offer the features that you need in your app? An example: it includes a fs-events system, to monitor for changes in files, but it is crippled to work around a bug in one version of Mac OS X, and so in the end, one probably has to write their own file-monitoring logic for each platform (or copy the Chromium code, and then modify it). Additionally, once you start modifying the base libraries to add the features that you require, how do you merge with the changes that the Chromium team inexorably publishes?

Are you making bets on Dart or (P)NaCl staying with the platform in the long run?

Hi, maybe it's a stupid question, but could you write a C application that makes use of these libraries? I mean, when you talk about integrating with the Chromium source code you mean cherry-picking some code and dropping it into your C++ code or you're talking about linking it at compile time?

Awesome post, though.

Do you have a link to the documentation? And if there is no documentation for this many year old project why is that? Is using it in this manor different than the explicit goals of that code (which from what I understand is to only support chrome)

So, you're not using any of the rendering parts?