- Blade templating language. I don't need yet another templating syntax to learn, especially one that isn't analogous to others I know and are common among other frameworks.
- I really can't imagine going back to an active record based ORM. I've learned too many hard performance lessons from Doctrine1 and rails at this point.
- Facade/proxy pattern based classes. I think as they are implemented in the actual framework, these are done correctly. However, I think the userland understanding of this pattern is often lacking and leads to a lot of glorified singletons that are some how touted as acceptable because they call them facade/proxy based.
In the giant lineup of frameworks, ranging from something as simple as SlimPHP or silex, all the way to enterprise targeted frameworks like Zend Framework 2, I just don't see why I'd ever pick Laravel as the go-to solution in any use case.
All the major frameworks are just as decoupled, but as soon as you start selecting off the "native" defaults for things like templating and ORM you lose integration features that have been built into other areas of the framework to support that specific library.
- Blade templating language. I don't need yet another templating syntax to learn, especially one that isn't analogous to others I know and are common among other frameworks.
- I really can't imagine going back to an active record based ORM. I've learned too many hard performance lessons from Doctrine1 and rails at this point.
- Facade/proxy pattern based classes. I think as they are implemented in the actual framework, these are done correctly. However, I think the userland understanding of this pattern is often lacking and leads to a lot of glorified singletons that are some how touted as acceptable because they call them facade/proxy based.
In the giant lineup of frameworks, ranging from something as simple as SlimPHP or silex, all the way to enterprise targeted frameworks like Zend Framework 2, I just don't see why I'd ever pick Laravel as the go-to solution in any use case.