Server-side JavaScript and Jaxer

Here is a shortened example from Aptana:
<script runat="client"> var name = getName(); alert(name); </script> <script runat="server-proxy"> function getName(firstName) { var name = ... // do something interesting return name; } </script>

Here the call to getName() must return the name, so it runs synchronously. Jaxer provides a getNameAsync() method that accepts a callback (and uses an async XMLHttpRequest call) but it's hidden deep in a technical FAQ page.

Obviously the synchronous code reads better, but until JavaScript has some kind of continuation support to make async calls look synchronous, [functionName]Async should be the only -- or at least default -- means of server communication. Otherwise all Jaxer apps will seem perceivably slow to users, not to mention preventing all other browser windows from responding while requests are active.