I'm with you, because I believe composer will become a (even more than already) standard.
Relying on it doesn't seem to be far fetched today already.
And certainly it's not a PITA to resolve that system dependency anyay.
Not even on Windows!
I agree working with bake templates is no joy.
Any solution is welcomed.
Using Twig for bake templates sounds not so bad to me.
But be sure you will get a hell a lot of requests to use it for the views by default then ;-)
Sure it has to be documented and people have to learn it.
But there is already a documentation (+ a community etc.) and not all CakePHP "users" have to learn it, only if they want to work on bake templates.
In any case I prefer Twig over Mustache or any other template engine like Smarty *horror*.
Also other solutions like using asp tags seem prone to break sooner or later or for some users respectively.
"Perhaps people just need to update their app's composer.json so the autoloader is correct."
If there was a way around that it would be more sexy.
Can you "include" the content of file in composer and using that content for additional dependencies?
My question though is would we want to have a dependency like Twig while you decided some time ago that you don't want to have Doctrine?
I probably compare here apples with pears since Doctrine was a replacement for something more integral as Twig was...