According to Henri Bergius, the next version of the Midgard software will be PHP5 only:

It took us a while to get here, but Midgard is finally entering a release cycle which will drop support for PHP4. The reasons are quite clear: simplicity and speed. The whole PHP4 end of life business has caused quite a bit of discussion in the PHP community.

The group chose to go PHP5 only for speed reasons (like advancements in their Query_Builder component) and the new features that PHP5 will allow in their MidCOM component.

According to Henri Bergius, the next version of the Midgard software will be PHP5 only:

It took us a while to get here, but Midgard is finally entering a release cycle which will drop support for PHP4. The reasons are quite clear: simplicity and speed. The whole PHP4 end of life business has caused quite a bit of discussion in the PHP community.

The group chose to go PHP5 only for speed reasons (like advancements in their Query_Builder component) and the new features that PHP5 will allow in their MidCOM component.

Henri Bergius has posted this new item on his blog today talking about a real hurdle overcome - having MidCOM up and working on PHP 5.1.

Thanks to the efforts by Solt and Piotras, we finally have the MidCOM, the Midgard Component Framework running on top of PHP 5.1.

While we got PHP5 support into Midgard already in August 2004, the big issue has been the tens of thousands of lines of code in the MidCOM framework that had several PHP4 constructions.

You can grab this latest release with the CVS version combined with updates from Subversion to get things up and working with PHP 5.1.

Henri Bergius has posted this new item on his blog today talking about a real hurdle overcome - having MidCOM up and working on PHP 5.1.

Thanks to the efforts by Solt and Piotras, we finally have the MidCOM, the Midgard Component Framework running on top of PHP 5.1.

While we got PHP5 support into Midgard already in August 2004, the big issue has been the tens of thousands of lines of code in the MidCOM framework that had several PHP4 constructions.

You can grab this latest release with the CVS version combined with updates from Subversion to get things up and working with PHP 5.1.

In a new post on his blog today, Henri Bergius looks at the Zend Framework and some of the community effects/opinions that have been popping up.

The general community feeling on Planet PHP seems to be quite scared, as the new framework "threatens" to change the way PHP applications are developed, by providing a common set of tools and development methodologies. This is obviously a big change for everybody used to work either in the free-form fashion, or using one of the community-built frameworks.

However, even though I'm a developer in one of the PHP application frameworks, I see the need for some standardization. Now the common ground shared between all the different PHP frameworks is just the language itself, forcing all projects to focus on building lots of low-level plumbing infrastructure instead of focusing on the features that could differentiate the applications.

He talks more about the need for consistency, some about the Framework from a "Midgard point-of-view" (including the separate parts), and a wrap up of how he views the current status of the project - and what they might be doing wrong...

In a new post on his blog today, Henri Bergius looks at the Zend Framework and some of the community effects/opinions that have been popping up.

The general community feeling on Planet PHP seems to be quite scared, as the new framework "threatens" to change the way PHP applications are developed, by providing a common set of tools and development methodologies. This is obviously a big change for everybody used to work either in the free-form fashion, or using one of the community-built frameworks.

However, even though I'm a developer in one of the PHP application frameworks, I see the need for some standardization. Now the common ground shared between all the different PHP frameworks is just the language itself, forcing all projects to focus on building lots of low-level plumbing infrastructure instead of focusing on the features that could differentiate the applications.

He talks more about the need for consistency, some about the Framework from a "Midgard point-of-view" (including the separate parts), and a wrap up of how he views the current status of the project - and what they might be doing wrong...