tag:blogger.com,1999:blog-8279854.post2933962784216535984..comments2007-07-16T22:45:23.636-04:00Comments on Stan's Space: Mired in quicksandStan Rogershttp://www.blogger.com/profile/13819463953609361042noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8279854.post-85234042002380571562007-07-16T22:45:00.000-04:002007-07-16T22:45:00.000-04:00Nice redesign, btw. Green is good. :-)Nice redesign, btw. Green is good. :-)Karenhttp://www.blogger.com/profile/09384620776384912278noreply@blogger.comtag:blogger.com,1999:blog-8279854.post-62204355559062720212007-07-02T21:42:00.000-04:002007-07-02T21:42:00.000-04:00I tried that particular generousity tack, Rob, but...I tried that particular generousity tack, Rob, but after a while it just stopped making sense. It's sort of like wrapping LotusScript in LotusScript in order to isolate your code from changes to the LotusScript language.<BR/><BR/>In any case, the new verson will have a set of classes implementing a common interface, making db choice easier (mySQL is the wild card in this game -- there's no guarantee that it will remain free as in beer much longer, and ISPs may begin to drop it as a standard feature).Stan Rogershttp://www.blogger.com/profile/13819463953609361042noreply@blogger.comtag:blogger.com,1999:blog-8279854.post-15947755213792338092007-07-02T20:54:00.000-04:002007-07-02T20:54:00.000-04:00Hrm. At the risk of giving too much credit, is th...Hrm. At the risk of giving too much credit, is there any chance they were trying to insulate an API-like interface of their own from possible changes to the vendor's API? I've seen that done before, but only in a case where there were an awful lot of moving parts and most of them weren't under the dev's control. Oh, and the dev was paranoid about one particular thing. <BR/><BR/>The premise was that the vendor could change the names of their functions (and the parameters as well) without affecting most of the other moving parts. I thought it was juuuust a bit much (not to mention of questionable utility even granted the premise), but apparently it was a case of "twice burned forever shy" with this particular developer - after a couple of bona fide disasters, he insisted on doing this to every system he worked on.<BR/><BR/>Probably giving way too much credit, but as you know my philosophy on another person's code is always to assume there was a reason at the time. Not always a *good* reason, of course. :DRob McDonaghhttp://www.blogger.com/profile/00531055903349471245noreply@blogger.com