Something I find really strange/frustrating with a few recent frameworks (Laravel included) is their overuse of static methods. You have these singletons floati

Something I find really strange/frustrating with a few recent frameworks (Laravel included) is their overuse of static methods. You have these singletons floating through the framework which maintain state (Request, Session, Logging etc) but you can only ever access them statically. Seems like bad practise to me. What if you want to swap out Request for a mock during unit testing; since you've hard coded the Request class throughout your controllers how would you switch to a RequestMock class? What happens if you were dealing with more than one request (e.g in a HMVC setup).