|
Posted by Chung Leong on 01/03/06 00:14
Balazs Wellisch wrote:
> I'm not sure I understand your point. What exactly do you see as a problem
> in the development process?
Too much emphasis on feature addition. Too little on quality assurance.
There is something wrong when the development team is talking about
what to do/break in PHP 6 when Apache 2 support in PHP 4 is still
unsettled.
> Well, sure I am generalizing since we're having a discussion about the
> merits of open source development. It is in fact a necessity for open source
> to "release" software in an experimental state. Most projects have nightly
> builds that can be downloaded, worked on and then released again. This is
> how things get done. This is why open source is more powerful. Anyone can
> download the software and contribute to its development. Potentially there
> could be tens of thousands of programmers working on a project, fix bugs,
> add features, etc. No software manufacturer can compete with that.
But we are not having a discussion about the merit of open source
development. Why are people so eager to turn every discussion into the
merit of open source?!
> It sounds to me like you're a little bitter about something that went wrong
> and perhaps you lost some of your objectivity in the process. Why don't you
> elaborate a little more on your problem? Perhaps we can help!
Not bitter, just dismayed at the direction that PHP is heading.
Paradoxically, as they try to make the technology more
"enterprise-ready," it's becoming more hobbyish. I can't give out too
much details about my own project. I can only say it is a software
deployed in some important government agencies. It's nerve-wrecking
enough making sure that my own code doesn't fail. The last thing I need
is more uncertainty. Low margin for errors and low tolerance for
risks--that I associate with an enterprise environment. Unfortunately
the PHP illuminati seem to think that enterprise-ready means namespace
and what not.
Navigation:
[Reply to this message]
|