Symfony releases land on a predictable schedule, but the signal-to-noise ratio in release notes is low. This series distills each version to what actually changed the way you write Symfony applications.
Symfony 3.3: when services stopped being a configuration nightmare
Symfony 3.3 shipped May 29th. It’s the release that changed how I think about service configuration. In hindsight, it was basically a preview of what 4.0 would make the new default. The autowiring problem Before 3.3, Symfony’s DI was powerful but verbose. Every service had to be declared explicitly in services.yml with its arguments listed. Autowiring existed since 3.1, but it was opt-in per service and had enough edge cases to bite you. Teams either wrote mountains of YAML or leaned on third-party bundles to cut the noise. ...