It's a very common behaviour in a require.js architecture (coupled with this, we don't have this kind of issues if we bannish the `new` keyword). When a method is called form another file (scope) we need to ensure that `this` is right.