The module "app" depends on mod1, so this should render
RENDERED! from a directive defined on mod1
The module "app" depends on mod2, so this should render:
The module "mod2" does NOT depend on mod1, so this should NOT render:
RENDERED! from a directive defined on mod1
... but it does... Because app depends on both mod1 and mod2
What it should be is, for mod2 to use mod1 stuff, it MUST require it as a dependency.
Why is this bad? Because it makes it IMPOSSIBLE to enforce modularity in angular without some kind of preprocessor to somehow parse all the templates and understand which module belongs to which template and... no... stop... just stop....
So, Angular's super lame then right? No, it's not super lame. It's still super awesome. But this part about angular... Yeah, this is a bad part :-(