gmosx

some more thoughts on appengineJS here: http://www.gmosx.com/blog/agVnbW9zeHIPCxIHQXJ0aWNsZRipwwEM/o...

I would like to see support for "use strict" and some more aggressive optimizations. And hopefully, Java7 with support for invokedynamic will be released soon.

Ok, it was a 'play' of words. I wanted to point out that after you put 90% of the effort to create an application you need to put 90% effort to actually deploy it in production. Google App Engine helps here.

But the fact that AppengineJS (and Rhino/RingoJS that powers it) runs on GAE is a distinctive advantage IMO.

> 1. You either didn't see my previous post or have no useful response.

Javascript is a great language with some mistakes. a lot of the mistakes (including some you mentioned) are fixed in Ecmascript 5. I programmed in Ruby from 2002 since 2009, and I am happy I switched to JavaScript: I prefer the syntax, I totally love prototipical inheritance, I love to object literal notation, and the use of closures everywhere.

> 2. Sorry, let me rephrase my point here. You can reuse code, but not all code. Any code you could reuse could also be re-used in another languages using tools like GWT, py2js, j2js, etc, mitigating server-side javascript's advantage here.

as I said, pure bs.

> 4.5.

JavaScript has some advantages and some disadvantages to Python. AppengineJS is for people who know JavaScript (just about every web developer) and do not want to learn Python. If you know Python, just stick with the Python SDK.

no prob, thanks to CommonJS it was extremely easy to switch from Narwhal to the RingoJS: www.ringojs.org

> 1. No it's not. It's mediocre at best. See my previous post.

of course it is

> No you can't, not anymore than you can reuse Java code between client and server with GWT. The difference between a browser and a client environment is just so great.

pure bs, obviously you don't know what you are talking about. I am reusing extensively between server and client, not only for simple stuff like validations, but also to render graphics (have a server side canvas implementation that renders to svg), to perform web crawling (I use a simple version of envjs and jQuery/sizzle on the server side for crawling), i use the same template engine on server side and client side, etc, etc...

> 4. Ever heard of Jython?

Why would I be interested in Jython??!

There might be some problems but it's great to know that Google system administrators (instead of me) are taking care of it. When I hosted my application on EC2 twice I almost lost all my files due to hardware problems. I had to spend all night preparing a new server, not funny. There are no servers to fail in App Engine, I love that!

yeah, whatever ;-)

And a useful video:

http://code.google.com/events/io/2009/sessions/OfflineProces...

>I'd really wish for some AppEngine developer to tell me how's the proper way of designing entity groups.

here are some helpful links:

http://code.google.com/appengine/articles/datastore/overview...

http://code.google.com/appengine/articles/datastore/overview...

http://code.google.com/appengine/articles/scaling/contention...

In fact, the syntax is one of the things I prefer in JavaScript (vs for example Python), along with Prototypical inheritance...

You can't just port your application to App Engine. You have to start from scratch. Google enforces all the right constrains to force you to write scalable apps. The killer feature is that there is no need for system administration or maintenance. No need to setup dns rules to make your email go to the recipients, no need to update apache or linux, no need to setup an xmpp serrver, etc. Plus, you can leverage Google's battle tested infrastructure. The icing of the cake is that you can now use the internet programming language, ie JavaScript, while still having access to the vast collection of Java libraries. A match made in heaven if you ask me!

1. JS is a great language. 2. You can reuse code on the server and client side, no mental context-switch. 3. Javascript VM's are generally faster than Python VMS. 4. Rhino provides access to the vast collection of Java libraries 5. App Engine is the easiest way to go from a toy application to a industrial strength, production application

Indeed, Rhino is such an important project but still it does not receive any attention.

Most definitely, yes