|
|
Posted by Henk verhoeven on 07/26/07 18:06
Ivan Marsh schreef:
> On Tue, 17 Jul 2007 23:35:55 +0200, Henk verhoeven wrote:
>
>> Ivan Marsh wrote:
>>> Unless you're doing this as a programming project download one of the
>>> many that already exist, install it and customize it to your liking.
>> BEWARE: the existing one will soon release a new version.
>
> <snip bullshit>
>
>> IOW, sooner or later you need to update, and the longer you wait the
>> harder it gets. In the best case you have preparerd for this, use CVS or
>> some other version control system to reapply your changes and have unit
>> tests so you can quickly veryfy wheather everything still works as
>> expected. But we don't live in an ideal world, your updating effort can
>> easily become your updating nightmare.
>>
>> Greetings,
>>
>> Henk Verhoeven,
>> www.phpPeanuts.org
>>
>> PhpPeanuts is an application framework you can use to boost your
>> productivity. It has a specialization layer that allows you to keep your
>> own code separated from framework code. Changes are usually specified
>> upto individual methods. If an error occurs in development it outputs a
>> walkback so you can at least see where it comes from. Building unit
>> tests for your own code is nevertheless highly recommended, just like it
>> would be if you had built everything from scratch.
>
> So you're telling people not to use other people's software at moment
No, i am just warning for problems inherent to reuse of third party
software and giving suggestions how they may be managed.
> and promoting your own the next?
1) I did not say that it is a good idea for this particualr project. Of
course other issues then maintenance are to be adressed too.
2) The info *is* relevant to the subject. IMHO Keeping your own code in
separate files - separated from third party code - is an effective way
to deminish the maintenance problems i have described. The frameworks
website contains explanations and examples of how to do it. Developer of
software that is to be reused by other developers can do the same, they
do not need the phpPeanuts framework to do so, they just need to
understand how it is done. I would really like them to do so, that would
make software reuse a lot easier for me too.
3) I am and have not been not making a single penny out of releasing
phpPeanuts as open source and documenting it. I can only build and
maintain the software because i use it myself and it saves me time. (I
can't say that about the documentation.)
>
> Sorry... but I try not to use software written by hypocritical morons.
Sounds more like you are trying to kill the messenger. But just in case
you would like a serious answer: Of course keeping your own code in
seperate files does not remove dependencies to the third party code.
Class and method names, inherited and called by your software can still
change (and be removed) over versions and therefore break your code. If
you want to make an analysis of the amount of change in the frameworks
api's as an inverse measure of my hypocrisy, i will be happy to send you
old versions. (There will be substantially more change when going from
1.x to version 2.0, but it is not yet designed, i will publish about
that as soon as i know what it will be).
Navigation:
[Reply to this message]
|