• 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
Mac Automation Scripting Guide [was Re: New Calendar Scripting Guide from Apple]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Mac Automation Scripting Guide [was Re: New Calendar Scripting Guide from Apple]


  • Subject: Mac Automation Scripting Guide [was Re: New Calendar Scripting Guide from Apple]
  • From: has <email@hidden>
  • Date: Tue, 22 Mar 2016 12:33:01 +0000

Jean-Christophe Helary wrote:

> 2016/03/22 19:27、Schmidt, Michael <email@hidden> のメール:
>
>> And don’t forget the new Mac Automation Scripting Guide
>
> Wow, really nicely designed...

And full of ASTONISHINGLY SHIT CODE.


Seriously, what idiot decided to recycle the notoriously garbage Essential Subroutines, code that is so appallingly poor it's not even wrong? Hand up please, so I can tell you straight to your face just how embarrassingly incompetent you are to your face. I swear, it's almost like there's a conspiracy of obtuse stupidity, deliberately working to make AppleScript appear even more moronically broken and unsustainable than it already is. The only thing that AS code does is make the confusingly entangled JXA code look good by comparison, and JXA is an incompetent busted obfuscated piece of crap that I wouldn't wipe my ass on for professional work. Good grief.

Oh, and for those thinking I'm being terribly unfair, don't say I'm ever afraid to stick my money right where my big mouth is:

    https://github.com/hhas/applescript-stdlib

As-per it's dragging on twice as long as intended, but except for the Web library (which is still to complete) all the commands are more or less finalized, I'm adding documentation and examples, and I'm slowly grinding towards full[ish] test coverage despite a marvellously obscure and nasty bug deep in the AppleScript implementation that causes it to crash my test scripts through no fault of their own. THAT is what professional, production-quality AppleScript library code looks like, not this infantile copy-pasta toy nonsense. And I've also said I'll turn that code over to Apple wholesale, so they can stick it in the OS and stop embarrassing themselves with garbage like this, because THAT QUALITY OF PRODUCT is the VERY MINIMUM that AppleScript USERS DESERVE.


I am up to my eyeballs this week (and probably next too) in artwork automation work, but if Apple gives the slightest fucks about putting out high quality AppleScript documentation I will be happy to discuss my rates. I may be rude, opinionated, lazy, and burnt out, but I understand this wretched wonky language better than anyone else on the planet, not to mention I used to work at one of the best educational publishers in the land and already pounded Apress's chaotic tome into a mostly excellent coverage of the subject, so know a thing or two about putting together documentation that doesn't totally suck.


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: Mac Automation Scripting Guide [was Re: New Calendar Scripting Guide from Apple]
      • From: Jean-Christophe Helary <email@hidden>
  • Prev by Date: Re: New Calendar Scripting Guide from Apple
  • Next by Date: Problem with Outlook 2011
  • Previous by thread: Re: New Calendar Scripting Guide from Apple
  • Next by thread: Re: Mac Automation Scripting Guide [was Re: New Calendar Scripting Guide from Apple]
  • Index(es):
    • Date
    • Thread