tag:blogger.com,1999:blog-5797187.post6701190637282139590..comments2024-02-18T16:27:52.414+01:00Comments on Christof Damian: eZ winter conferenceChristof Damianhttp://www.blogger.com/profile/01602827735606341943noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-5797187.post-62661468118074823742009-02-01T14:38:00.000+01:002009-02-01T14:38:00.000+01:00I think it is not generally wrong to rewrite, even...I think it is not generally wrong to rewrite, even from scratch. As F. P. Brooks, Jr. writes in "The Mythical Man-Month, chapter 11 "Plan to Throw One Away", citing a study by Lehman and Belady:<BR/><BR/>"All repairs tend to destroy he structure, to increase the entropy and disorder the system. (...) As time passes, the system becomes less and less well-ordered.(...) Each forward step is matched by a backward one. Although in principle usable forever, the system has worn wout as a base for progress. Furthermore, machines change, configurations change, and user requirements change, so the system is not in fact usable forever. A brand-new, from-the-ground-up redesign is necessary."<BR/><BR/>That might be the case for a software that started as a "one man show" and grew uncontrolled over the last 4 years after it matured with version 3.7/4.0.<BR/><BR/>Anyway. Reinventing the wheel isn't the right idea either, for example in the critized creation of a new template engine in FLOW3 instead of using Smarty, which is quite established.<BR/><BR/>Keeping alive the 4.x tree, easing the migration from 4.x to 5.x as mentioned above and trying to introduce and learn from some modern software development techniques and theories should give all of us the chance to go on with our business (staying with 4.x and using our well defined development processes) or to satisfy our interest and our need to improve steadily by experimenting with 5.x.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5797187.post-79338042153346121062009-01-31T14:55:00.000+01:002009-01-31T14:55:00.000+01:00Though I'd like to say otherwise, I've heard simil...Though I'd like to say otherwise, I've heard similar rumblings surrounding the TYPO3 5.0 release.<BR/><BR/>However, from what I've seen of TYPO3 5.0 so far and some of which has been back ported to TYPO3 4.3 has been quite slick.<BR/><BR/>In any case, many of the larger content management systems open source and proprietary are all undergoing major rewrites to become serious content management frameworks.<BR/><BR/>As such, many folks from many CMS background will be looking around seriously to go with a basic framework, content management system, enterprise CMS, or a content management framework.Michael Cannonhttps://www.blogger.com/profile/00403071468957826677noreply@blogger.comtag:blogger.com,1999:blog-5797187.post-53709483399542295812009-01-30T09:09:00.000+01:002009-01-30T09:09:00.000+01:00We will have to see what the future brings. At the...We will have to see what the future brings. At the moment it looks like typo3 5.0 will be a point where many people might take the opportunity to look at other options. <BR/><BR/>And typo3 certainly seems to be doing something wrong for us now, because we wouldn't invest the time looking into different solutions otherwise.Christof Damianhttps://www.blogger.com/profile/01602827735606341943noreply@blogger.comtag:blogger.com,1999:blog-5797187.post-80441183440971985612009-01-30T07:13:00.000+01:002009-01-30T07:13:00.000+01:00Thanks for the comments on eZ and TYPO3. I've been...Thanks for the comments on eZ and TYPO3. I've been working with TYPO3 for 6 years and have similar feelings about the developer "show-off". Then again, with the devs showing off, we've got an extremely flexible framework that's quite adaptable to most any environment.<BR/><BR/>For more, I've been writing about TYPO3 business, social, and technical aspects at http://www.acqal.com/acqal-blogging.html.Michael Cannonhttps://www.blogger.com/profile/00403071468957826677noreply@blogger.com