That is just a way to create artificial job security.  Rules is another word
for standards.  The standards are loose enough that you can modify them.
Without standards, there would be no Internet, no POP3, etc.  Frameworks can
eliminate spaghetti code that is inevitable when 4 different developers all
code with their own style on the same site.   Frameworks promote team-based
programming.  If you always code alone, then you are right.  You don't need
them.

John McKown
President, CEO 
Delaware.Net, Inc.
888-432-7965

-----Original Message-----
From: Claude Schneegans [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 06, 2006 2:07 PM
To: CF-Talk
Subject: Re: OOP, why me?

 >>The biggest reasons I see for using frameworks are:
-code reuse
-flexibility
-maintainability
-documented code

Well, IMHO these are just clichés.
- code reuse? I don't see what in non framework application makes 
reusing any code any more difficult.
- Flexibility? Framework means rules, how can rules add flexibilty?
- Maintainability? By someone who knows the framework, may be, but for 
other (most of the time), it is like hell.
- documented code? Any code should be documented, in a framework or not. 
Frameworks do not create documentation.

Anyway, any experienced programer will end up with his own way to design 
applications,
this is some kind of a framework, and it is the best one, because it is HIS.

Gee I'm using a framework, and I didn't even know about it ;-)

-- 


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:234287
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to