T3 sounds a lot like Ember-cli's structure:
- T3 Services -> Ember helpers
- T3 Modules -> Ember components
- T3 Behaviours -> Ember mixins
I've also found that the code I'm writing in Ember is much easier to test because of these abstractions.
- T3 Services -> Ember helpers
- T3 Modules -> Ember components
- T3 Behaviours -> Ember mixins
I've also found that the code I'm writing in Ember is much easier to test because of these abstractions.
- T3 Services -> Angular Services
- T3 Modules -> Angular Modules
As for behaviors, they seem closer to the Controller concept in both frameworks, rather than mixin.