• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [FYI] more sdef-based library stupidity
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [FYI] more sdef-based library stupidity


  • Subject: Re: [FYI] more sdef-based library stupidity
  • From: has <email@hidden>
  • Date: Sat, 04 Jun 2016 10:34:50 +0100

Shane Stanley wrote:

> On 4 Jun 2016, at 4:21 AM, has <email@hidden> wrote:
>
>> Bypassing AS's established dispatch rules when dispatching commands that use `use`-imported terminology is NOT my complaint.
>
> OK.

OK what? Do you at least agree it's a bug? If not, please provide your technical and UX rationale for the observed behavior so we can productively critique that. Cos right now it seems like I'm doing all the work and you're doing all the sarc and I much prefer the other way around.


>> My complaint is that it's buggering up how those commands' parameters are evaluated. It actually makes those parameters appear as if they're being evaluated within the *library* script instead of within the script in which they're actually declared. (Hence my initial flawed hypothesis.)
>
> Sorry, but I still don't see the sky falling.

The sky is not falling. AppleScript is broken. There is a difference. Mostly the difference is between having a rich, vibrant, growing pro- and end-user scripting and automation ecosystem, and one that ossified and moribund and limited to hardcore legacy users. If Mac automation dies the world will still turn; computer users will simply be even more disempowered and beholden to vicarious vendors than before. Like the apocryphal slow-boiled frog or Stockholm syndrome victim, your response to every new defect flagged is to shrug and say "So what?" Perhaps you think you're defending AppleScript's honor or audience by pretending it isn't waist-deep in a rut - how long till you decide to say something? When it's waded in up to its neck? When it's entirely submerged? When it's dragged its hapless users down with it? There is something fundamentally wrong about a mature platform that MULTIPLIES defects as the years go on, and willful blindness to that does not help.

Honestly, there's a reason I say it's clear Apple don't give a crap about AppleScript and should just come clean and officially give up on it (that is, move it to legacy status and end further development outside of essential maintenance). At least that would allow the possibility of some other team in the company to have a fresh crack and try something new (c.f. Swift); perhaps let the JSCore folks have another crack at their original idea of making JS a simple, embedded, programmer-friendly alternative to the constant pain and increasingly worthless effort of trying to implement decent Apple event support. Not ideal but there are worse things that could happen: like no sanctioned end-user scripting or desktop automation at all.

Tell you what, I'll go write up the bug ticket now I've grokked what's going on, and then you can dupe it to help bump it up the priority list, and prove you're not just running apologetics for the Death By A Thousand Cuts AS team.

has
_______________________________________________
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


  • Follow-Ups:
    • Re: [FYI] more sdef-based library stupidity
      • From: Shane Stanley <email@hidden>
  • Prev by Date: About the use statement
  • Next by Date: Re: ASObjC: Get Most Recent File or Folder
  • Previous by thread: Re: [FYI] more sdef-based library stupidity
  • Next by thread: Re: [FYI] more sdef-based library stupidity
  • Index(es):
    • Date
    • Thread