I used to think the same thing, but then I ran into the problem where my large app had circular dependencies which require.js/AMD does not support. Naturally, AMD supporters blame you and your project's architecture, but it is not uncommon to have some circular dependencies in a large app.
The work-around is to use require.js in commonjs style or to add hacks into your architecture. Not fun.
The work-around is to use require.js in commonjs style or to add hacks into your architecture. Not fun.