I guess I don't get your point. It seems to me that the code is more obviously upgradable if I use WASP (or any other OS framework for that matter). Imagine this scenario:
1. My company writes 8 major applications this year w/o using a framework of any kind.
2. PHP 6.0 comes out.
3. I have 8 applications to herd through the upgrade process.
Or imagine this scenario:
1. My company writes 8 major applications this year using WASP.
2. PHP 6.0 comes out.
3. I have 1 application to herd through the upgrade process (WASP itself).
4. There is a team helping me upgrade it.
Of course maintainability is about more than just dealing with upgrades so I like the idea of my approach to development being the same as everyone elses so that if changes need to be made and I am on a beach somewhere I don't need to be interuppted.
Slashdot Mirror
My firm is a fairly big fan of WASP (http://wasp.sourceforge.net/). Check it out.
I guess I don't get your point. It seems to me that the code is more obviously upgradable if I use WASP (or any other OS framework for that matter). Imagine this scenario: 1. My company writes 8 major applications this year w/o using a framework of any kind. 2. PHP 6.0 comes out. 3. I have 8 applications to herd through the upgrade process. Or imagine this scenario: 1. My company writes 8 major applications this year using WASP. 2. PHP 6.0 comes out. 3. I have 1 application to herd through the upgrade process (WASP itself). 4. There is a team helping me upgrade it. Of course maintainability is about more than just dealing with upgrades so I like the idea of my approach to development being the same as everyone elses so that if changes need to be made and I am on a beach somewhere I don't need to be interuppted.