Re: Libraries and effiency
Re: Libraries and effiency
- Subject: Re: Libraries and effiency
- From: Tommy Bollman <email@hidden>
- Date: Fri, 6 Aug 2010 18:55:24 +0200
Hello.
Hey Tommy, it's a logical non-sequitur to equate 10 year old billy-box bugs with a modern Mac system.
Well, it really should have been like that, but it aint! This is basically what happens when say your download some python code, or Tcl, or Perl, or Java for that matter, just to realize, (hopefully within an hour), that it doesn't work because what you downloaded assumed that your frameworks and libraries were in the same state as the developer. (That is how it is.) Then if you update your frameworks to support what you newly installed, then you are at risk of braking something else that relied on what you had from before. It can be a pesky, and annoying issue to solve this tasks. Everything would have been a lot easier if everybody used version numbers in the file names. AppleScript Users comes in several flavors. Some just want to use the functionality of some code, without a single idea and clue about what is going on. That user is a whole kind of different user to someone that downloads some java, pearl or python source, in order to use.
I find the ideal solution to those problems to ship the code either within what you distribute, or embedded in a script library server which is a far more practical approach. This forces the developer to supply a new and tested version of the client scripts in order to get totally rid of the old ScriptLibraryServer upon an upgrade, or he can just leave the user with both of them, maybe at the cost of some bloat, but everything will still be functional. And not the least leaving the developer with an as easy as possible development environment which supports the usage of libraries.
On 6 Aug 2010, at 17:01, Philip Aker wrote:
> On 2010-08-06, at 04:53:12, Tommy Bollman wrote:
>
>> Wether that mechanism is implemented all over the place or not; I find that particular mechanism to be a bad idea as a whole.
>
> Well, I think it's good because it's a reasonable solution to the layering problems that occur in a mixed system like Mac OS X. Furthermore, it has consistent behavior.
>
>
>> It may be preferable from a developers point of view, but it isn't so for a user,
>
> I'm a user too. In fact I first learned about it as an OS X user because I was unaware of CFPreferences in CarbonLib on MacOS 9 and still used resource forks.
>
>
>> which then will have to track down what is a miss, because he hasn't got that version installed, and the system are showing know errors about missing files because it found something higher up in the tree.
>
> I've never encountered that problem.
>
>
>> -I believe that unique names is the way to go, or that one library file can only reside in one physical path. -I may agree on the benefits of being able to implement something either globally like with the /Library/Preferences v.s. those in ~/Library/Preferences, *but it stops right there*.
>
>> Tetsuro is taking this approach further, by allowing for adding folders to the search path. And then one may possible end up with a situation that was referred to as "the DLL nightmare" in yesteryears, where you have to go an inspect which version of the library you got, and which is called, -it is really an unfruitful way to spend time when such situations are encountered.
>
> Hey Tommy, it's a logical non-sequitur to equate 10 year old billy-box bugs with a modern Mac system.
>
>
>> I think different versions of something should be reflected by their filenames, in order to trap what is installed and not installed, when using such a load mechanism as Tetsuro's.
>
> I think what's needed here are some guidelines for library loader developers.
>
> It will be to the benefit of users that each loader implements a few consistent behaviors so they can assess the capabilities of different loaders without having to shuffle their libraries around.
>
> I will post a sketch much later on today and take comments.
>
>
> Philip Aker
> echo email@hidden@nl | tr a-z@. p-za-o.@
>
> Democracy: Two wolves and a sheep voting on lunch.
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> AppleScript-Users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> Archives: http://lists.apple.com/archives/applescript-users
>
> This email sent to email@hidden
>
Best regards
Tommy Bollman
--------------------------------------------------------------------------------------------------
Mollison's Bureaucracy Hypothesis:
If an idea can survive a bureaucratic review
and be implemented it wasn't worth doing.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden