It’s not server-side markup. It’s all in HTML files. All of the code in this post is in HTML files. Under the covers we compile our expression language into Javascript.

The best argument is that our solution is integrated so you don’t need to worry about finding an Ajax framework or a widget toolkit – we give you all of that for free. We also give you an integrated services platform for Java, Ruby and PHP (.NET and Python are in progress). The net result of this is that you focus on building applications instead writing integration code.

Another argument is that in the simple cases like basic forms most frameworks make that look easy. The real value from Appcelerator is when you want to do more complicated things. Our expression language greatly simplifies complex tasks. Having the ability to control the user interface “look” and to send/receive both local and remote messages using one simple expression language is very powerful and it does, in fact, result in a lot less code.

Hope that answers your questions. I would be happy to answer any other questions you have as well.

What would you say (try to convince me) if I said: I could just use a form, with an action to /login/request and I’d achieve the same (call to an endpoint with some parameters). I could make the message asynchronous using my favorite Ajax framework, see if the response is successful ad based on that change the layout. I would not have coupling between my client code (HTML/JavaScript) and my server (maybe /login/request is a Java servlet or is mapped to an ASP.NET handler).

I Would like to know more, thanks!