> "All routes defined in one single file instead of procedurally in each controller (performance wise this is terrible cause you're running a bunch of regular e

> "All routes defined in one single file instead of procedurally in each controller (performance wise this is terrible cause you're running a bunch of regular expressions on each and every request. augh)" Have you timed it? And do you have a flexible alternative measurably faster that can drop in/ Are you taking in to account route caching? Not everything has to be in one file. RouteServiceProvider gives you a place where you can programmatically determine which route files, if any, you want to process. > File structure doesn't adhere to PHP league standard So what? And... "all php code should in in src or tests..." That doesn't even seem to be documented anywhere. PHP code could live in /config (like... you seem to want above?) - but 'config' isn't /src or /tests.