Hands-on With App Engine’s New Runtime

Re:Hands-on With App Engine’s New Runtime by walid on Monday May 06, 2013 @06:37AM (#5661695)

My bet is on node.js meaning JavaScript :)

[ Parent | on HN ]

Re:Hands-on With App Engine’s New Runtime by alcuadrado on Monday May 06, 2013 @09:49AM (#5662356)

Knowing that the V8 team dislike javascript so much that they created Dart (and Lars Bak says this openly), it's hard for me to think about google including node.js to AppEngine

[ Parent | on HN ]

Re:Hands-on With App Engine’s New Runtime by markokocic on Friday May 10, 2013 @02:42AM (#5684951)

Because noone can order anyone at Google to work on anything except what he likes to?

[ Parent | on HN ]

Re:Hands-on With App Engine’s New Runtime by erlichmen on Monday May 06, 2013 @07:41AM (#5661834)

AppEngine is not build to support node.js async model, my bet is on Ruby.

[ Parent | on HN ]

Re:Hands-on With App Engine’s New Runtime by walid on Monday May 06, 2013 @08:11AM (#5661910)

I'm not a web developer so I have to ask whether Ruby is that different from Python so that another tool chain gets added and maintained.

Edit: your point about node.js makes sense though.

[ Parent | on HN ]

Re:Hands-on With App Engine’s New Runtime by portmanteaufu on Monday May 06, 2013 @09:26AM (#5662192)

I've never used App Engine before -- what is it about its design that precludes Async?

[ Parent | on HN ]

Re:Hands-on With App Engine’s New Runtime by ronbeltran on Monday May 06, 2013 @06:41AM (#5661702)

That seems closer

[ Parent | on HN ]