NYCPHP Meetup

[Rainelemental]

Hi
since composer joined our toolkit and the php-fig standardized PSR things changed a lot, now frameworks are more such an ecosystem with different components that cooperate together.

With this in mind, feel free to choose any frameworks that are PSR compliant and you'll do right, or even better choose your components and build your own framework.


From my iPhone

On Feb 7, 2013, at 10:09 AM, Lester Leong <lester.bleong at gmail.com> wrote:

> I've used a little bit of Cake in the past but now am using CodeCharge for production development in my company. It's a bit tight and restrictive, but extremely, extremely fast and well-suited for complicated reports and grids (ie, CRM, lists, etc) and other back-end functionality.
> 
> With that said, I'm looking at new frameworks for my own personal development work, but other than Cake, I have no clue about any of the new ones out there. Can anyone provide a good rundown of the popular frameworks out there - ie, Laravel, CodeIgniter, Kohana, and the other ones Brent mentioned above - based on their experiences? Like pros, cons, etc.
> 
> On Thu, Feb 7, 2013 at 9:32 AM, Brent Baisley <brenttech at gmail.com> wrote:
>> Not too long ago I decided to sit down and quickly sample all the popular frameworks again (Symfony, Slim, Laravel, CodeIgniter, Yii). I didn't want to spend more than an hour getting each up and running and playing with it. Laravel was on that list and I was eager to try it since it was designed really with only PHP >=5.3 in mind.
>> 
>> I never really got very far with it since it requires mcrypt to work even in it's most basic form. I did not have mcrypt installed, so that added time. It required DocumentRoot to be set and a writeable directory (storage/views) to work. A bit of extra work just to get a page up and ate into my self imposed 1 hour limit.
>> It largely (completely?) uses static class references, which I am not a big fan of. It is convenient since the static references are  easily accessible from anywhere. But it means you can't overload it and use your own classes without some difficulty. Like a lot of frameworks, you need to commit to it and the way it does things.
>> 
>> That said, Laravel is certainly a framework I would have on the short list of options. Symfony is also much better in v2 and they are taking a module approach. For example, Twig is now standalone.
>> 
>> On Jan 14, 2013, at 2:32 PM, Yitzchak Schaffer wrote:
>> 
>> > On 01/14/2013 05:52 AM, Peter Sawczynec wrote:
>> >> Can anyone offer me any thoughts, what you've heard,  background info or
>> >> real world experience with Laravel?
>> >>
>> >
>> > ExpandTheRoom (an agency in Manhattan) uses Laravel, from what I've heard.
>> >
>> >
>> > _______________________________________________
>> > New York PHP User Group Community Talk Mailing List
>> > http://lists.nyphp.org/mailman/listinfo/talk
>> >
>> > http://www.nyphp.org/show-participation
>> 
>> _______________________________________________
>> New York PHP User Group Community Talk Mailing List
>> http://lists.nyphp.org/mailman/listinfo/talk
>> 
>> http://www.nyphp.org/show-participation
> 
> _______________________________________________
> New York PHP User Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
> 
> http://www.nyphp.org/show-participation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20130207/10e024e9/attachment.html>