2. It's also available. http://bundles.laravel.com/search?q=twig
3. Laravel focus on Event, so you can just set a listener to `laravel.language.loader` event and replace to anything you want it to be. Check http://www.keithloy.me/2012/04/yaml-config-files-in-laravel/
4. Same with Logging, just change https://github.com/laravel/laravel/blob/master/application/c...
2) Why not simply use PHP for templating?
3) Using YAML would be just as bad, if you want to use something use something standard for localization like gettext or XLiff.
2). See: http://twig.sensiolabs.org/ (Why yet another template engine?)
3). Personal preference I guess but I hate gettext. I much prefer the pattern of using labels in your template (e.g. menu.item1) and then looking up that label in the desired language file e.g. messages.en.yml. And I've never had a problem with translators working with YAML files (i.e. the syntax is easy for them to grok)
I'm agree that standardization would be just fine(c), and I like the Twig syntax, but I think the "YATL, we should use Twig" argument is not relevant.
1). Rolling its own ORM rather than using Doctrine.
2). YATL (yet another templating language). I wish the PHP world would just standardise on Twig.
3). Localisation seems a bit basic at the moment and it's a shame you have to define messages in a PHP array rather than something more portable like YAML.
4). Would have been great if it used Monolog for logging.
On the plus side, I like the clean design and their approach for events looks cool.