You could do that but it's not a good idea at all, your application becomes dependant on your "clever" routing (forcing Laravel to guess based on the URL which method on what controller should be executed, instead of telling Laravel explicitly) and loses a lot of flexibility.

If you absolutely must do it you could use RESTful controllers which is a middle ground (you need to define your controllers as part of your routes, but not the individual methods) or you could write your own function that parses the URL to determine the controller and method, but it's not a good idea.

citricsquid said:

Forcing Laravel to guess based on the URL which method on what controller should be executed.

Therefore making the performance a little bit slower ON EACH REQUEST.