Javalobby - Comments for "Flow3: PHP's Answer to Java's Spring?"

You're right that too many

rainwebs — Wed, 13 Feb 2008 08:22:41 -0500

You're right that too many frameworks can be a problem to beginners. But, Robert tried to describe why they don't use Zend e.g. as the base framework. For me, with a stronger Java background, they try to get what the Java community already has with Spring. This persuades me that Flow3 will have its place in the PHP community.

Springsteam Blog - Next Generation Java Development

oh the joy, yet another new

skoop — Tue, 12 Feb 2008 18:00:59 -0500

oh the joy, yet another new PHP framework. just what we needed ;)

Truely, for PHP's sake, it would've been better if they'd picked an existing framework and rewrite the CMS to be based on that. Zend Framework, symfony, it's frameworks like that, which really should be used instead of re-inventing the wheel once again. With so many frameworks to choose from, it's just going to confuse people who are relatively new to PHP.

That said, it's of course good to see the typo3 people are trying to stay active and always reconsider old code. The best way to keep innovating.

This is the place for

rainwebs — Mon, 11 Feb 2008 15:26:57 -0500

This is the place for further details:

http://forge.typo3.org/projects/show/flow3

Robert started to check in code. But, nothing to analyze for DI details at the moment.

Springsteam Blog - Next Generation Java Development

Are there any examples of

emilong — Mon, 11 Feb 2008 11:53:53 -0500

Are there any examples of how the DI works?

-----------------------------------------------------

Emil Ong
Chief Evangelist
Caucho Technology, Inc.
http://www.caucho.com/

Looks very interesting. Ma

mjais — Mon, 11 Feb 2008 02:24:43 -0500

Looks very interesting. Maybe I should give PHP another chance :-)

Markus

http://www.codekite.com

... in other news PHP

cowwoc — Sun, 10 Feb 2008 23:29:40 -0500

... in other news PHP community members reported that productivity has dropped like a rock in previous months. As we speak, experts are wading through XML trying to figure out what went wrong.

Spring is a bandaid and makes little attempt to fix the underlying problem. What's next? An new framework that abstracts Spring and Typo3 so your code can be portable across either one? At some point you've got to stop abstracting on top of frameworks that are abstracting for other frameworks. Furthermore, developers are spending too much time ensuring their code is portable across multiple databases when in reality most software never changes databases during its lifetime. It is true that "premature optimization is the root of all evil" but I argue the same is true for premature abstractions.

"Jumping of a cliff" is the

rainwebs — Sun, 10 Feb 2008 15:13:16 -0500

"Jumping of a cliff" is the right description ;-). When I changed to Typo3 3.8 using the TemplaVoila extension I needed about 2 weeks to get my template running. Not till then I could create the content I intended to when starting the project. But, with todays Typo3 4.x releases everything is easier. There are a lot of books now that help much to get things running. I think Typo3 5.0 will be the release that can be an alternative to Joomla/Drupal/etc. in the context of user experience. I expect that some of the Joomla guys, with complexer sites, will change, because Typo3 has the better core for such requirements.

Springsteam Blog - Next Generation Java Development

Javalobby - Comments for "Flow3: PHP&#039;s Answer to Java&#039;s Spring?"

You're right that too many

oh the joy, yet another new

This is the place for

Are there any examples of

Looks very interesting. Ma

... in other news PHP

"Jumping of a cliff" is the

Javalobby - Comments for "Flow3: PHP's Answer to Java's Spring?"