Angular-translate 2.0 released

You are right, dirty check is not the best thing when it comes to performance. However, we've updated the directive to only set up watches when needed. Which means, when you don't change the language at runtime, but kick off some $digest cycles, they don't get re-evaluated. So this should be an performance boost. Filters always set up watches, if you use filters, well... deal with it. You could use the directive. angular-translate isn't the answer for everyone and that's okay because this is not what it should be. It solved a problem for me and people like it, which is why I still develop this module.

For some cases angular-gettext surely makes more sense, angular-translate gives you just a much higher integration into the angular world and solves more problems like async loading, fallback languages, pluralization, language negotiation etc etc.

Chose what fits best for you! :)

IMO, they way gettext handles translations is way superior than the key->value model for many reasons:

1. You never will run out of keys.

2. Makes code much easier to read with a real language on messages instead of keys that can't possibly describe the whole message.

3. While writing code, you don't need to stop to think in a new key to add your message, go to the key->value list file and add it there. You just wrap you message with _('') and it's done.

4. Easier to write messages that have variables inside using sprintf or similar.

It doesn't support gettext, it solves the problem differently with translation id's. Stick with angular-gettext if it fits better to your needs, that okay :)

But I mention here, that we also see how we can bring such kinda support. Like using english texts as translation ids.

Yeap you're right, the changelog generation didn't work very well because our commit messages weren't always very specific. This will become better in the future.

For further information, checkout this G+ post: https://plus.google.com/+PascalPrecht/posts/V5GtNp1tU27