That's not really the point here. Let's face it, ZF1 was a great piece of work if you look at it now, and you can keep using it if you do want to also maintain it in future. We all learned what the limits of singletons and registries are, and some even got say ZF1 is crap (I'd say short sighted :) ), without realizing that comparing it to things like Symfony 2 is like comparing an old steam/coal locomotive to a gasoline car.
I honestly don't think ZF1 will fit requirements of software development projects you will face in the future, and that's why some ideas were dropped, some components were kept and others completely discontinued. This does not just apply to ZF, but to anything you find out there. You are not following a company in its choices: you are following new design paradigms that are used by the community and by other developers nowadays. Some "new" discoveries (other programming languages applied them a lot of years ago) were made and now are being used to rebuild new frameworks. This is how it has always worked so far (not just in software engineering). So it's not "someone" pressing a reset button: it's all of us. You should learn to live with legacy or move on and rewrite everything... Or get involved and be part of the wheel that changes all this :) Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On 4 November 2012 19:53, [email protected] < [email protected]> wrote: > Hello Mike, > > Unfortunately we are in the same situation. > We started to use ZF1 back in 2007. > We have invested a lot of time and effort to build our own library with > reusable > components based and following the philosophy of zf1. > We have spent months (years) to master zf1. > And jet, we have to start everything from scratch again! > It is an endless story. > "The tired horses get killed!" > I have not been active member of the community because I have been busy > working > on our projects. > So I have not been part of the discussions about the design patterns etc. > in > ZF2. > I also couldn't believe we have to start over again. I think ZF2 has great > ideas. > But there should be a way to migrate the existing code not multiply the > time and > effort of so many people by 0. > The sad story in this industry is that if you follow somebody (we follow > Zend) > you are doomed to be always second. > We have to buy again new books, attend seminars invest again huge amount > of time > learning the new. things. > It is like pushing the reset button of your computer. Every once in a while > somebody pushes the reset button and we all start from scratch again. > And we are not allowed to complain, because we get everything "for free". > It is a whole industry around such projects. To keep it going there should > be > such restarts. > "Instead of learning, you better learn how to learn fast!" > We better start refactoring everything to use ZF2, right now. And in 5 > years ... > or even sooner they again will push our reset button. :) > This is the way how it is! > > Best Regards, > Stoyan Cheresharov > > > > > Mike Wright <[email protected]> hat am 3. November 2012 um 19:30 > geschrieben: > > Hi all, > > > > As work has progressed on zf2 I'm finding it more and more difficult to > > find zf1 info on the site. Often I can find what I'm looking for using > > very indirect routes, which shows the information is still there, but > > the direct links to things zf1 are disappearing. > > > > Because of that I'm becoming increasingly concerned that zf1 is becoming > > a horse with a broken leg just waiting for the coup de grâce. > > > > I've been working on a zf1 project that uses modules, has services > > attached to models (or is it the other way around :?) and have a > > significant investment in time and effort and am not sure I have the > > resources to rewrite the whole thing using zf2's much different design > > philosophy. > > > > What will happen to those of us tied to zf1? > > > > Thanks for any insight, > > Mike Wright > > > > -- > > List: [email protected] > > Info: http://framework.zend.com/archives > > Unsubscribe: [email protected] > > > >
