|
|
Posted by NC on 12/26/06 22:46
Tony Marston wrote:
> "NC" <nc@iname.com> wrote:
>
> > The best framework is no framework.
>
> I disagree. A framework, such has been built yourself from previous
> projects, will always save time and money by not having to rewrite
> (and debug) what has been written before.
But you don't need a framework for that. A well-structured code
repository will work just as well... Take what you need for
production,
leave the rest in the archives...
> > Frameworks help developers quickly and cost-effectively (with
> > "cost" meaning "development cost" rather than "total cost of
> > ownership") develop resource-hogging software
>
> But if performance and scalability are NOT important then a good
> framework could save you a fortune in developer costs.
Agreed. Conversely, if performance and scalability ARE important,
then the use of a framework during development would make a rather
large hole in your operating budget; you will end up using way more
dedicated boxes than you could have gotten away with if you steered
clear of frameworks...
Cheers,
NC
Navigation:
[Reply to this message]
|