Re: Security Update [Was: Re: Script Library Search Order]
Re: Security Update [Was: Re: Script Library Search Order]
- Subject: Re: Security Update [Was: Re: Script Library Search Order]
- From: has <email@hidden>
- Date: Tue, 26 Jan 2016 02:20:14 +0000
On 25/01/2016 21:46, Chris Page wrote:
On Jan 25, 2016, at 12:11 PM, has <email@hidden> wrote:
On 22/01/2016 02:02, Chris Page wrote:
Have you observed a specific performance issue with library lookup on 10.11-10.11.2 that you can report? There are several strategies in place to make it efficient.
Like caching? That merely replaces one problem with another. Honestly, AppleScript is fractal brokenness all the way down; beyond ensuring the security hole is plugged I'm doing my best to ignore individual instances of AppleScript Lame and Fail, as down that road waits only total insanity and I've enough screws loose as it is.
So...have you encountered a performance issue or not?
Currently no, because I'm not looking for performance issues in the
library loader. Nor do I see any point doing so, since
correctness>performance, and the "correctness" of this whole magical
search path "feature" is seriously questionable. So even if I did
measure significant performance problems I still wouldn't Radar them,
because those priorities are completely backwards.
I'm just trying to get some practical development done, making the best
of what exists. I want to get these "standard libraries" off my hands
within the next couple weeks, as they've already gone from "amusing
procrastination" to "thousands of dollars of free unpaid work..."[1]
Right now the biggest lags I'm seeing are in SE, especially when
displaying an error in the result pane (at least half a second); any
lags that might be due to the library loader will be masked by all the
other crap.
The biggest problem I have with libraries right now is not loading time,
but their staleness after editing due to them not reloading
automatically on the next run. Yes, I'm aware there's also the desire
for OSA scripts to persist between runs to consider, but SE is an
editor, not a launcher, so if linked code's changing from under the
script being worked on then picking up those changes immediately should
be its first concern. If clever caching is getting in the way of AS/SE
doing the right thing there then it's the caching that should be ripped
out, and the motive for putting in that caching in the first place
seriously re-examined.
Regards,
has
[1] If you're serious about getting your library system off the ground,
you *really* ought to be talking to me and the rest of the list about
adding a polished, proven, standard AS library to 10.12/10.13. You want
to see your loader being put to good use: well, here I am putting it.
And I'm not writing these libraries for *my* benefit: I'm doing it for
AppleScript users. But these libs need to be transferred to Apple and
bundled with AS to make any actual difference, because right now the AS
community has neither the formal reuse culture nor the distribution
infrastructure to drive widespread library adoption *independently*. Nor
will it ever develop that culture or infrastructure until and unless
*all* AS users are *already* convinced of the huge benefits to using
libraries; which means it has to work out the box. Typical
chicken-vs-egg. You're noticably silent on the topic thus far, which
isn't an encouraging sign that this won't just be another "...and
utterly wasted work at that" on my part, so if you can throw us a bone,
on- or off-list, it would do a power of good as I'm now at the
80%-complete point (so only another 80% left to do:p).
_______________________________________________
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