Thanks! I'm not sure if it's already possible with Kelp::Less, but I created to give you a way to "categorise" routes. So instead of one large file full of 'get', 'post' calls, you can add them in separate modules, then your main .pm will just pull them altogether. In larger applications it just makes it easier to find things. So, you could separate user functions from products, for example.
package MyApp;
use KelpX::Sweet;
maps ['User', 'Product'];
package MyApp::Route::User;
get '/view/:id' => 'Controller::User::view';
package MyApp::Route::Product;
get '/view/:id' => 'Controller::Product::view';
KelpX::Sweet may only be beneficial over Kelp::Less in big projects, just to file code away in easy to find places. Now the foundations are there, I can add some extra features to KelpX::Sweet::Route and hopefully do some cool stuff with KelpX::Sweet::Controller, as that does absolutely nothing at the moment! If you want to do something small for prototyping and such, there is nothing wrong with Kelp::Less at all.
It is still early days for this module, so I'm interested myself to see what comes of it :)
Cheers,
Brad