On Tue, Feb 5, 2013 at 3:58 PM, Paolo Fragomeni pa...@async.ly wrote:
Sounds like you have a specific use case/requirement, use the tool thats
right for you :)
I spent a little time with node-chrome last night, thanks for adding
to the project description.
Time permitting, I'm hoping to send a
They're not the same, which is why I said he's oversimplifying what
node-webkit does. This is basically chrome in application mode talking to
an http server.
On Tuesday, February 5, 2013 8:20:23 AM UTC-8, psema4 wrote:
On Mon, Feb 4, 2013 at 7:00 PM, mgutz mario.l@gmail.com javascript:
Perhaps oversimplification to one person is optimalsimplification to
another.
On Tue, Feb 5, 2013 at 2:16 PM, mgutz mario.l.gutier...@gmail.com wrote:
They're not the same, which is why I said he's oversimplifying what
node-webkit does. This is basically chrome in application mode talking to
In all fairness to both projects, it's probably more fair to say the
difference is in project scope, not in code complexity. Talking about
complexity is a little silly here, anyway. I mean, you're already good for
several hundred thousand lines of code once you have node + v8 + chrome
How does this compare to node-webkit or appjs?
On Monday, February 4, 2013 1:04:26 PM UTC-8, hij1nx wrote:
*node-chrome(3)*
A tiny module for building desktop apps. It's really simple and uses the
chrome runtime.
*Here's the module.*
https://github.com/hij1nx/node-chrome/
*Here's an
