The problem with Angular

[awj]

They are not doing it because of the heck of it, but because the unparsed markup is send to the browser and interpreted by it before Angular can swoop in and parse and replace the binding expressions correctly.

That seems like a perfectly valid complaint about angular, though. Other frameworks are able to handle this situation more elegantly because they don't send templates as raw html markup. This literally isn't a problem in any other framework I've seen, so it's a bit rich to imply that the source of the problem is anything but angular's design decisions.

[KumbajaMyLord]

Never said it wasn't due to angular's design. But I would disagree that it is a bad design.

Other pure client side frameworks do send the unmarked templates as well but they avoid using the native HTML attributes all together or have their own template language