> Of course not. But currently the image for PHP is that it's ONLY > meant for web scripting. Even as it can be used in various other > places too.
That has always been our position. "PHP focuses on the Web problem". That has been the design roadmap, if you will, from day one. > I think it would clean some air too if there was a group which > stands behind the certain main ideas behind PHP. > Like for example, CS. That issue pops up quite frequently and > somewhat litters the mailing list with these long debates whether > or not PHP should be fully CS or not. If there was some group > which says that no, this will not change, maybe we wouldn't have > to waste time fighting over it? (or some other similar issues) Hrm, but as a group we have stated numerous times that this will not change. That doesn't seem to have stopped these long threads. You think that if we write it down in a document which nobody will read, that will somehow change things? I am not against having a roadmap document, of course. I think it would be a cool thing to have, I just wonder how useful and accurate it would be. It is very hard to predict what things people will be interested in looking forward. > They post that STATUS email to their dev-list weekly or so. > (Yes, we have TODO..but who really reads that? :) If nobody is reading the TODO, why would they read this roadmap? > >IActiveScript hack. One thing you would think is marked in stone is that > >PHP is a server-side language and it would never end up sitting alongside > >Javascript embedded in a browser as a client-side language. Yet it can > >now do this. > > Of course, but is this part of the general vision of PHP? :) No, PHP's vision is to solve the Web problem, as it has always been. > No roadmap or group or anything can prevent people doing whatever > they like. But what is 'official'? It could prevent duplicate work > and release some eyes,hands,minds to other tasks. And also, > if it contained stuff that never ever will be done, prevent some > useless emails going out? (like this one :) Sometimes duplicate work is good. Different approaches to the same problem. Other times work is duplicated because one approach is moving quickly enough and someone really needs to solve the problem quickly. But yes, the information should be available. But I still wonder how in the world you are going to convince everyone to update a file that describes what they are working on and what they intend to work on. We can try and see if it works. ie. make a decree that thou shall always maintain the TODO file. > >It leads to forking of the project, which in itself isn't bad, but it is > >cooler if we can hold things together and work as a group to accomodate > >the various ideas and approaches in a somewhat organized manner. > > See above. I would really like to avoid any forking of PHP..but > if you're suggesting that that's the only way to go..fine. > Is the current way of doing things _organized_ ? For a very sharp focused vision, you need a small focused team. So yes, in that sense the only way to get that is to fork PHP and only have a couple of people working on it. With a large team of people working on aspects that interest them, PHP is going to move in several directions at once. To me this is a good thing. A few nudges to get everyone to move somewhat in the same direction is about as much as we can do without basically telling people to take a hike. -Rasmus -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
