Here is my wish-list: Changes that support the simple. Currently SF2 is a leap for developers. Some concepts are extremely difficult to get your head wrapped around and there are external initiatives that imo are trying to improve this in their own ways (e.g. KnpRadBundle). I am not saying that the SF2 base distro needs to be more RAD like, but I would love to see more interaction with initiatives that are trying to reduce the learning curve. Some ideas to think about: Defaulting to a one application Bundle development flow, with the option to support multiple application bundles if needed. (ala KnpRadBundle) More generators. REST is something I have started to move away from in SF2. SF2 has some great initiatives in REST, but the APIs are still immature. For instance we have FriendsOfSymfony/FOSRestBundle, fsc/hateoas-bundle, and schmittjoh/JMSSerializerBundle (also the SF2 Serializer for very basic serialization). 3 packages, that compared to their counterparts in other frameworks (and in other languages) are difficult to get working as you would expect. With REST being such a dominating focus of my current development, this would be enormous for me. Support standards (http://jsonapi.org/) and simplified implementations would be my focus on these areas. Other frameworks and other languages could really influence SF2 in this as well. Both Jango and Rails have a vastly improved REST setup over SF2, and frankly so do some PHP counter parts.
On Jun 3, 2013, at 4:40 AM, Marco Pivetta <ocram...@gmail.com> wrote: > There's a couple of things that I will need to figure out for ZF3 that I'd > like to push in the DependencyInjection builder: mainly inlining factory code > (tricky, but it will bring quite some performance improvements) - not sure > I'll make it for 2.4 though. > > I don't know how much of the EventDispatcher code is actually built for > extension, but a lightweight of it that removes internal method calls could > squeeze out some more performance. Also here: it's a question of inlining > code... > > On my side, I'm even more than 100% against a cache component - that's just > yet another wheel until FIG comes out with something. Otherwise it's just > another interface you can adapt to. If you need exoteric caching support, > pick an already existing component and write an adapter for it - even if you > use ZF it won't bite you because it has "Zend" in its name, I promise ;) > > Marco Pivetta > > http://twitter.com/Ocramius > > http://ocramius.github.com/ > > > On 3 June 2013 09:00, Jérôme Vieilledent <lolautru...@gmail.com> wrote: > Hello > > Patrick Allaert already pointed out performance issues with autoloader. I > know this is Composer related but I think this can really be improved (see > patrickallaert.blogspot.be/2013/03/benchmarking-composer-autoloading.html). > > Cheers > > Le 3 juin 2013 08:52, "Fabien Potencier" <fabien.potenc...@gmail.com> a écrit > : > > Hi all, > > As Symfony 2.3 is going to be released today, that also means that work on > 2.4 can start now. > > We have 4 months of development, so if there is anything that you think we > need to work on (or things that you want to contribute to), that's the right > time to discuss it. Based on the topics that are the most popular, we might > then create dedicated teams that focus on them. > > Besides the few pull requests that already target 2.4, I have one topic that > I want us to work on for 2.4: **performance**. What can we do to improve the > performance of Symfony (on real-world apps, not for a simple hello world > page)? What are the main pain points? The first step would be to create a > suite of benchmarks for the critical components (HttpFoundation, HttpKernel, > Routing, EventDispatcher, ...), and then see how times can be improved. > > So, if Symfony 2.4 was just about 1 new major change, which one would it be > for you? > > Fabien > > -- > Fabien Potencier > SensioLabs CEO - Symfony lead developer > sensiolabs.com | symfony.com | fabien.potencier.org > +33 1 40 99 80 80 > > -- > -- > If you want to report a vulnerability issue on Symfony, please read the > procedure on http://symfony.com/security > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > --- You received this message because you are subscribed to the Google Groups > "Symfony developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to symfony-devs+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > -- > If you want to report a vulnerability issue on Symfony, please read the > procedure on http://symfony.com/security > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Symfony developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to symfony-devs+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- > -- > If you want to report a vulnerability issue on Symfony, please read the > procedure on http://symfony.com/security > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Symfony developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to symfony-devs+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en --- You received this message because you are subscribed to the Google Groups "Symfony developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to symfony-devs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
