In addition to phil j's comment, I would like to point out that angular is a framework built on top of several emerging standards for evolving HTML. The polymer project provides a number of browser polyfills to allow you to use things like shadow DOM, template tags, all part of the Web Components spec. It also provides Model Driven Views and Web Animation, along with several others. Angular is built with the same ideas and is getting moved on top of polymer.

Angular TypeScript bindings are available. I'm not sure about polymer. I also don't think it necessarily wise to build yet another framework directly on top of any compile-to-javascript language without getting a good feel for what advantages you could obtain. Thus, I would love using the Angular bindings to generate apps I would otherwise write with HTML and JS.

It's possible that doing this would inform some really cool options directly through WebSharper, removing the Angular dependency entirely. Of course, you then lose the benefit of a fairly substantial team effort building a framework like Angular.

Angular extends html in a great way, providing a binding framework, declarative animations, easy routing, large number of third party extensions/directives etc.
Angular Controllers would be great in f#, being just a function having Services automatically injected as arguments, being able to share code, domain model and call rpc methods with the Server side.
And writing directives using Websharper would be a charm.
I believe Websharper and Angular could fit very well together. This idea also goes trough my head for quite some time now :)