tag:blogger.com,1999:blog-36345871.post3381176969859514676..comments2023-07-11T05:39:57.966-07:00Comments on Perl Alchemy - notes of a programmer: Nothing is foreverzbyhttp://www.blogger.com/profile/04636763782334128869noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-36345871.post-32089990558466129782009-07-27T04:49:39.201-07:002009-07-27T04:49:39.201-07:00Agreed, I've sometimes thrown a library away d...Agreed, I've sometimes thrown a library away during a refactoring. But I think you're talking about something different : *planning* to throw a library away; choosing to use a set of components which I know I'm going to move away from later.<br /><br />Now I agree that there are kinds of scaffolding which you plan to throw away, eg. code-generators like Instacrud, but I don't think that the relationship your code has with a library (ie. calls to it scattered all over the place *in* code) is this kind of "short-term relationship". <br /><br />When you know you are using something as temporary scaffolding, you definitely want dependencies to it to be ruthlessless demarcated and encapsulated in time and space. (Ie. in one place and at one fixed time.)<br /><br />Library-use doesn't follow this pattern.Composinghttps://www.blogger.com/profile/01739889615635395138noreply@blogger.comtag:blogger.com,1999:blog-36345871.post-56796150563868807512009-07-27T00:29:11.550-07:002009-07-27T00:29:11.550-07:00Hi Phil,
Haven't you changed or completely go...Hi Phil,<br /><br />Haven't you changed or completely got rid of some library when refactoring your code? In my practice that happens, it happens with my own libraries and with external ones, and it happens mostly at the beginning of the coding, but sometimes later as well.zbyhttps://www.blogger.com/profile/04636763782334128869noreply@blogger.comtag:blogger.com,1999:blog-36345871.post-89845252871724681802009-07-26T16:16:28.861-07:002009-07-26T16:16:28.861-07:00Hmmm ... surely a library is a collection of compo...Hmmm ... surely a library is a collection of components that can be included in your application. That's not a relation which you expect to disappear. What happens if your library suddenly went out of date? You'd replace it with a new one?<br /><br />The nearest thing I can think of to a disposable library is, say, a library of mock objects that simulate a database, which may get replaced by the real database at some point.<br /><br />However, even these you'd normally want to keep around for running unit tests etc.Composinghttps://www.blogger.com/profile/01739889615635395138noreply@blogger.com