I also feel somewhat dirty when using custom attributes, and I admit I preferred xmli-sh HTML and namespaces a-la ng:attr.. but is there any practical difference?
We're dealing with applications here, not documents, and even in the latter case, your views regarding ids and classes are extreme.
Angular templates, more than just markup, are the skeleton of your application. The markup they generate is as semantic as you make it.
Actually, I hesitated before posting... I had ruled sarcasm out because purely snarky posts are usually frowned upon here, and your parent post was asking a legitimate question...
That being said, we obviously agree on the topic.
In all seriousness though. That is kind of the correct answer to the parent. There's kind of this weird attachment to a whole bunch of weird 'best practices' in the design front. Many of them conflicting, many of them not well thought out. (There are some good ones coming out).
It's similar to twitter's bootstrap. Designers think it's horrible, if you believe the kind of blog with grey text on a grey background. But I can't believe people would recommend against it when they've seen the alternative.
That's some cool stuff you make with your band, btw. What do you play?