I don't agree on any comments about technology A going to destroy B, C or D. It is not really the technology that will put an end to something is the software development community and the customers that will say what they prefer, want, can provide or have to use. A real case: anyone remembers the BETA and VHS videos? BETA was better but it was VHS which survived.
It is all like natural selection: only the stronger will survive. Use the technology wisely and you will be strong, otherwise it will not do you anything for you. About the remark about putting Struts/iBatis out of the scope of PHP. The only problem is that if you try to port something from one technology to another you must, beforehand, understand which critical(s) problem(s) does it solve and then implement it with the strengths of the new technology. If you make a mapping between the codes then you will not really gaining nothing by doing the port. I made my own small php-struts like implementation and worked quite nice and actually increase the quality, speed of my PHP applications plus my work efficiency. So I continued using and improving it. I also made 1 class that helped me achieve something very similar to iBatis with no complexity at all. In conclusion, good ideas/implementations can and should be re-used but with they must be thought on the correct context and implemented exploring the strengths/advantages of the new language/technology and, sometimes, with a lot of creativity. Pedro Salgado On 27/07/2005 13:07, "Daniel Perry" <[EMAIL PROTECTED]> wrote: >>> 3. PHP. I've done some PHP over the last couple years. >> >> PHP and Struts are not antithetical. There have been several ports of >> Struts to PHP, as well as Struts-like frameworks, such as Maverick and >> FuseBox. >> >> I'm not working in PHP myself, but if I were, you can bet I'd be >> porting both Struts and iBATIS. >> >> What we call Struts is not about Java, it's about an architecture that >> pushes logic away from server pages and into a control layer that we >> can configure via XML. >> >> -Ted. > > That is all true, but you'll find most php sites dont use anything that > complicated. And if they did, hosting would be more expensive. e.g. phpBB > is banned from most cheap shared hosting - it puts too much strain on > php/mysql in a high volume server. > > Also, java has been engineered to push things into layers. Php has not. > Also, java is OO. Php is not (or is, but badly!). I wrote an OO system a > few years back in php, and it was a nightmare. > The most annoying thing is > that assignment/method parameters clones objects - it doesn't reference it. > You can get round that by adding & in the right places. Only one nice OO > thing is the serialize funtion. > > So i would say that things like iBatis and struts fit nicely into the java > world. Give php-struts to the average php developer (i know lots of them) > and theyd smile, and politely tell you where you can stick it. > > Daniel. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
