[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: question regarding prelinking (was: (inc. note from dpkg developers) (was:Bug#XXXXXX: (far too many packages) needs rebuilt for prelinking))



On Saturday 18 Jan 2003 10:42 am, Yven Leist wrote:
> On Friday 17 January 2003 13:17, Emile van Bergen wrote:
>
> [interesting discussion about prelinking]
>
> > Make no illusions, nobody's going to use your utility functions
> > standalone anyway, outside of those environments.
>
> You might want to have a look at http://www.apple.com/safari/, KHTML and
> KJS were used for exacty that reason AIUI; then again maybe these
> components are not what you would have called utility functions, but
> still...

Which again shows _good_ design. Apple needed an html renderer, and a 
javascript processor, but not a UI toolkit, and this was available to them. 
If you only needed a javascript interperator and not an html renderer (say 
for scripting in your application) then you can do that too. Modularity is 
very important in design, if you think you can predict how your code will be 
used (do you think the khtml guys ever thought apple would use their code 
when they began?) then you are very mistaken.

Tom



Reply to: