I am starting a new project from scratch, this project is intended to be a responsive website, which mean performance on mobile devices is top priority. I would like to know some information about how angular:
How angular manages its resources and dependencies. are the files loaded in memory each time or they live in the memory during the web browsing. also is the use of RequireJS or AngularAMD a solution for this sort of situation?
I encountered a situation where I had a page containing tabbed views. in this situation, is it better to create a different view for each one of these views, or is it better to use the native implementation, where all views live on the same page and are loaded simultaneously? (for this case I saw something about the parallel - state)
I think you are focusing on these things way too early for the development phase of the project.
If you start simple, by concatenating all of your files into one and properly minifying and gzipping it on serving, you will spend only 20 minutes setting it up instead of fighting an async module loader. Code wisely and try to put your logic into independent modules from the start (which is a good idea not only for browser loading speed, but for maintainability). Moving to a loader is then something you can focus on where you already have something done.
Any benchmarks or tests on an empty Hello World app will be irrelevant anyway at the beginning.
Parallel states are useful if you need to maintain the context of the state deep into one of the tabs. Click through the wiki example to understand it. The feature isn't targeting performance, but capabilities of the router of maintaining multiple state trees.