I think that the Kernel::init() method should be removed altogether and the code moved to the front controllers (like is done in fabpot/Silex-Skeleton). I will do that for 2.3.

It is also related to #6828 as it will allow for a better decoupling.

imo the method shouldn't be removed , only its call being moved:

<?php
// ...
$kernel = new AppKernel('dev', true);
$kernel->init();
$kernel->loadClassCache();
// ...

About the decoupling between Debug and HttpKernel, I don't think removing this method would add any value, while the yet-to-come Debug component wouldn't be tied to the Kernel, the opposite isn't true apparently, if we just look at the constructor's second argument.

@bamarni the debug mode of the kernel is about controlling whether the cache should be reloaded automatically, and such other things. Registering an error handler and an exception handler in dev is better done by the front controller than the kernel IMO.

@stof : The debug mode of the kernel is also about controlling what we're currently considering to move (https://github.com/symfony/symfony/blob/master/src/Symfony/Component/HttpKernel/Kernel.php#L101), I don't think it is related to the dev environment, currently all those things are registered when I switch debug to true in my prod front controller too.

Does it make sense at all for the kernel to be serialized?