News for hackers. Stuff that matters.
Re:Chrome Is The New C Runtime by sanjeevr on Friday January 17, 2014 @06:02PM (#7079077)
Hi all,

I'm the author of the post. Happy to answer detailed questions on using Chromium as a Dev platform. Any suggestions for a follow-up post?

Re:Chrome Is The New C Runtime by icefox on Friday January 17, 2014 @07:58PM (#7079544)
"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.

Re:Chrome Is The New C Runtime by zwieback on Friday January 17, 2014 @06:07PM (#7079112)
Simple sample app would be great for the next post.
Re:Chrome Is The New C Runtime by nonane on Friday January 17, 2014 @06:24PM (#7079196)
I second this. Would love to see an actual app skeleton that links with Chromium's sources.
Re:Chrome Is The New C Runtime by sanjeevrad on Friday January 17, 2014 @07:09PM (#7079376)
Will keep that in mind for my next post, thanks.
Re:Chrome Is The New C Runtime by binarycrusader on Friday January 17, 2014 @09:50PM (#7079832)
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.

Re:Chrome Is The New C Runtime by presorted on Sunday January 19, 2014 @03:08AM (#7083810)
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?
Re:Chrome Is The New C Runtime by snirp on Friday January 17, 2014 @06:05PM (#7079101)
Are you making bets on Dart or (P)NaCl staying with the platform in the long run?
Re:Chrome Is The New C Runtime by sanjeevr on Friday January 17, 2014 @06:14PM (#7079145)
We aren't relying on Dart. (P)Nacl is a very interesting option which I'm willing to bet will remain with the platform.
Re:Chrome Is The New C Runtime by michaelwww on Friday January 17, 2014 @07:48PM (#7079501)
Now that you're not a Google employee, can you give an opinion on Dart's chances of making it into Chrome. Thanks.
Re:Chrome Is The New C Runtime by cliveowen on Saturday January 18, 2014 @05:38AM (#7080711)
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.

Re:Chrome Is The New C Runtime by icefox on Friday January 17, 2014 @07:55PM (#7079536)
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)
Re:Chrome Is The New C Runtime by swah on Friday January 17, 2014 @06:15PM (#7079153)
So, you're not using any of the rendering parts?
Re:Chrome Is The New C Runtime by nilsbunger on Friday January 17, 2014 @07:30PM (#7079456)
No, we don't use rendering components for our application. But that doesn't mean you (or anyone else) can’t.