On Thu, Aug 16, 2012 at 4:08 PM, Avner Zangvil <[email protected]> wrote: > Thanks so much for the explanation! I am currently considering which > underlying platform (node-webkit or app.js) to use as a basis for a unique > application environment that I'm developing. What would be your thoughts on > keeping in pace with future releases of Chromium and node? app.js addresses > this by packaging itself as a node add-on built as a patch for CEF.
node-webkit's code is kept up with newest node and Chromium's code, I sync Chromium's code to upstream every a few days, so you don't need to worry about it. And we're discarding the dependency of CEF now, next release of node-webkit will be based on Chromium's Content Shell, so it will be much easier for us to sync with chromium and reuse chromium's code. node-webkit will be more like a part of Chromium. As for which platform is suitable for your app, my suggestion is try writing a simple hello world for both ones and see which one is more easier, and also consider which one is more suitable for distributing your app in future. > P.S. I believe app.js runs node as a separate thread but in the same process > as CEF - not as a separate process. I thought app.js is based on CEF3 which is multi-processed, excuse me for that. -- Cheng Intel Open Source Technology Center -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
