I think points 1 and 2 are pretty strong. I've always felt reluctant about having your entire code base available to whoever opens the JS file. Maybe I'm just paranoid.
The real strength is reducing the transfer size. You're only sending what's needed by the client. Nice stuff, if it works as-advertised.
Also noteworthy is the new ability to treat the DOM as a resource from the server point of view. Extracting information and rendering view partials in realtime as well as placing event listeners for the DOM on the server can help get things done quite a bit faster. This is especially true since you can now work with the DOM near the scope of other server-side only resources making it easier to create prototypes and apps that have a high level of user interaction with them.
The real strength is reducing the transfer size. You're only sending what's needed by the client. Nice stuff, if it works as-advertised.