621 karma · joined March 4, 2010
He also acknowledged that Google is obviously building V8 for Chrome and not Node and shouldn't be expected to spend time and money on features that aren't beneficial to Chrome. One example of this is the time required to spawn a new V8 context, around 30ms. It could be made drastically faster if all security features were removed from the V8 boot process (not needed for server side trusted execution environments) but Google needs secure VMs for Chrome tabs and it wouldn't make sense for Chrome to spend time optimizing V8 for this use case.
I didn't get the feeling, however, as this article implies, that V8 is a "roadblock" for Node.
I'm not trolling, I'm just a big fan of open data -- especially community driven approaches.
"The Webian project is a not-for-profit venture founded by Ben Francis. Ben is a full time software engineer at a startup in Cambridge (England)."
"...when Mozilla Chromeless came along it was suddenly possible to rapidly develop a working prototype using standard web technologies like HTML, CSS and JavaScript. As a member of the wider Mozilla community this was an opportunity I couldn’t resist..."
https://github.com/maxogden/refine-uploader https://github.com/maxogden/refine-processor https://github.com/maxogden/refine-python https://github.com/maxogden/refine-ruby
do you have a couch replication endpoint exposed through your api?