/explore
|
You are here 
|
symfony.com | ||
| | | | |
tomasvotruba.com
Regarding Laravel, one of the biggest "no"s in 2022 was how it handles passing services around the project. I'm not talking about the facades or active records but **the static reflection container**. At first, it raised my blood pressure - we have a dependency injection, and everything must be passed via the constructor, right? Then I remembered a wise saying: "There are no best solutions, only trade-offs." |
|
| | | | | ||
| | | | |
richardmiller.co.uk
Background I am recreating Lime Thinking's current website [http://www.limethinking.co.uk] using Symfony2 [http://symfony.com/], much of the site is made up of what are effectively static pages. The main content of the page is stored as an XML file which then has the overall XSL template |
|
| | | | | ||
| | | | |
matthiasnoback.nl
Part I: Don't use the standard controller The general belief is that controllers are the most tightly coupled classes in every application. Most of the time based on the request data, they fetch and/or store persistent data from/in some place, then turn the data into HTML, which serves as the response to the client who initially made the request. So controllers are "all over the place", they glue parts of the application together which normally lie very far from each other. This would make them highly coupled: they depend on many different things, like the Doctrine entity manager, the Twig templating engine, the base controller from the FrameworkBundle, etc. |
|
| | | | | ||
| | | | |
blog.theamazingrando.com
The point of this post isn't to convince you of the usefulness of Dependency Injection there's been plenty of pixels spilled about it already. Instead, I want to talk about using Dry::Container to alleviate some of the pain points that DI introduces. |
|
| | | |||
