5 reasons to use KNP RAD edition
Dec 20, 2013
As an early user of Symfony2 (and even symfony1), there are things you learn after a few years.
Things you agree with, and things you don't exactly agree with. A typical symfony2 application is often composed of many coupled, non-reusable bundles, with (at least!) 4 or 5 ways to name routes, services, classes, etc.
Entities are in the CoreBundle, but only used in the FrontendBundle. Ha! Finally in the BackendBundle too. And then the word "consistency" comes to mind.
KNP RAD solves this problem by providing normalized ways of doing things. KNP RAD faciliates common tasks such as access to entity repositories, service creation, DI extensions and more. KNP RAD doesn't interfer, neither break an existing application. It is fully compatible with any other distribution. It allows you to do the way you want. Here at KNP, we develop using the RAD edition of Symfony2, and there's a very good reason. No, in fact, there are many reasons, but we'll start with just 5:
- It lets you focus on application code, not on non-reusable bundles everywhere (TM).
- It gives you consistency. You can have a mess if you really want one, but KNP RAD will lead you down a path of sensible naming (route names, for example)
- It is opiniated. But it is as flexible as any other Symfony distribution. So, very flexible.
- It is green. Well almost all the time. It's well-tested, even with functional tests, like in the real world. (Yes, an app kernel IS the real world).
- It is fast. Build a working app with it quickly using a wide variety of shortcuts that you can choose from.
So let's improve and ease our day-to-day work so we can focus on the important stuff! And even if the amount of features is not that enormous, there are a lot of small things that make it worth trying :)