Comments on: Third party code NOT considered harmful http://agylen.com/2005/04/09/third-party-code-not-considered-harmful/ Ugo Cei's Weblog Fri, 03 Sep 2010 17:56:19 +0000 hourly 1 http://wordpress.com/ By: Hendy Irawan http://agylen.com/2005/04/09/third-party-code-not-considered-harmful/#comment-256 Hendy Irawan Fri, 15 Apr 2005 09:34:13 +0000 http://agylen.com/2005/04/09/third-party-code-not-considered-harmful/#comment-256 BTW, this is a very nice blog template!!! I wish I have something so beautiful as this design..... ugh ugh... perhaps I should go to WPThemes ;-) BTW, this is a very nice blog template!!!

I wish I have something so beautiful as this design….. ugh ugh… perhaps I should go to WPThemes ;-)

]]> By: Hendy Irawan http://agylen.com/2005/04/09/third-party-code-not-considered-harmful/#comment-255 Hendy Irawan Fri, 15 Apr 2005 09:31:04 +0000 http://agylen.com/2005/04/09/third-party-code-not-considered-harmful/#comment-255 I agree with you completely. Besides, we can write Adapters in the future, if we somehow change the library... Another besides, why couple your application to some proprietary interface that you invented? For example, in the PHP world, anybody using PEAR DB will be dead easy to migrate to other DB libraries such as MDB and ADODB (maybe Creole as well), since they already have adapters for PEAR DB. That won't be situation had you wrapped PEAR DB in a proprietary interface. I agree with you completely.

Besides, we can write Adapters in the future, if we somehow change the library…

Another besides, why couple your application to some proprietary interface that you invented? For example, in the PHP world, anybody using PEAR DB will be dead easy to migrate to other DB libraries such as MDB and ADODB (maybe Creole as well), since they already have adapters for PEAR DB.

That won’t be situation had you wrapped PEAR DB in a proprietary interface.

]]>