WebConsults.EUQuicksearchKategorien |
Thursday, March 26. 20096 Things that suck at Symfony FrameworkTrackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
Slighty troll-y post I must say. first issue is more of a personal preference. Second is not just an issue with symfony, it's an issue with any framework or application that wants to grow and innovate. symfony has taken most of the pain out of upgrading by offering a clear upgrade path. Point 3 is again a personal preference. You could also view this as a strength, because it allows you to very specifically configure certain behaviour. 4. Hard to search? Symfony documentation is quite easy to search. And it even has completely searchable API documentation. The second point 4 is again a personal preference. You can by the way also do it in other ways, you're not forced to do it in view.yml. 5. Only part of the caching is active when you use the _dev.php environment instead of the production environment. Besides, clearing cache means issuing a single command.
Well it is a bit provocating this post,
thats why i used a less objective title, i could also use something like "Wishes i have to get better at Symfony"
and yes it covers my personal preferences, otherwise i would use a more objective title.
To the arguments,
1. is a disadvantage for me which is a fact.
2. Yes other Frameworks have also problems but solved it better
3. For me its a disadvantage cause if i configure things at too much places i don´t know where to search for if somebody else made it.
4. I´ve seen better Documetations
5. Running the CC command is not the problem, forgetting about and searching for the error is what costing time, and this happens at least once a week.
p.s. Sorry for late reply
If you are a mess programing it's not symfony's fault. Every framework gives you the oportunity to do things badly, that doesn't mean that you should!
|