Re: Scripting Better Applescript support requests !
Re: Scripting Better Applescript support requests !
- Subject: Re: Scripting Better Applescript support requests !
- From: has <email@hidden>
- Date: Mon, 06 Mar 2017 21:44:28 +0000
Jim Underwood wrote:
You can discount it all you want (all without any actual review of the code), but I and others have found JXA to be very usable in the context I described above. I know of, and have seen, the JXA code of several others who I would say have considerable expertise, and are developing some sophisticated solutions.
And I know of JXA and Scripting Bridge users who bought into them just
as enthusiastically as you, only to get royally stiffed by them later.
You're just just the self-selecting subset that remains after everyone
else all quit in disgust; what do you suppose that says about your
standards? Just because you're all experts in JavaScript and Software
Engineering doesn't mean you know squat about JXA; if anything, it means
you know even less than a totally self-taught AppleScripters does. (Do
you even know that application scripting != OOP? Cos it's not. 99% of
Real AppleScripters may not understand it, but 99.99% of Real
Programmers comprehensively MISUNDERSTAND it—and then spread their
wrongness to everyone else.)
I'm not kidding when I say AppleScript is the only supported solution
that is guaranteed to work correctly: not least because that's what
every scriptable app developer of the last 20+ years has built and
tested their apps against. AppleScript is the de facto implementation
standard, and anything that diverges from that will crap its pants at
some point, and JXA and SB diverge significantly. (Appscript worked
right only because I spent three years black-box reverse-engineering
AppleScript's internal behaviors until I could replicate them,
quirk-for-quirk, 99.9% or better.)
And as for me being the world expert in Apple event bridges: don't think
I'm bragging—I'm CONDEMNING. Unlike all your millions of professional
software developers I did not have the benefit of a swanky CS university
education and richly rewarded programming jobs. I was an end-user who
taught himself how to write AppleScripts, and later write Python, C, and
a whole bunch of other ghastly Real Programming languages because I was
sick of the slop that millions of arrogant, ignorant professional
software developers tip all over us billions of users every day and
expect us to be grateful that they deigned to do anything at all.
I wrote AppleScripts because it was the only way to get the job done
right; I wrote appscript because it was the only way to get the job done
right, and now I write my own end-user automation languages so that
other end-users can do their own jobs right for themselves too. I'm the
world expert in this stuff not because I'm clever, talented, or
hardworking—because I'm not—but because everyone else—the real so-called
"professional experts"—are so fucking atrocious at their own jobs they
make even a dumb user like *me* look mindbogglingly competent in
comparison. Thousands of hours of my life spent, just because
professional software developers don't do their fucking jobs right, and
are so fucking insecure they can't even accept their own expert users
pointing out that they're wrong.
If you haven't run into JXA's reference form, type bridging, and
terminology defects, then 1. you're lucky, 2. lightweight, and 3. you're
not qualified to go round telling other users that JXA can do everything
AppleScript can, because that is Wrong, and you're just setting them up
to fail instead. If you don't wish to spend an hour or two researching
on the web to better learn how JXA does and doesn't work, that's
entirely up to you; I've told you exactly where to look, as that's where
you'll most easily find JXA problems posted by me and others. Just don't
expect me to do all that searching for you, not when it provides no
benefit to me. I've not asked much from this community over the last
decade—I've paid my original dues back many times over (that fecking
AppleScript book alone killed me)—but even when I ask for little things
like five minutes of everyone's time to go dupe two simple Radar tickets
that could've done something to salvage the mess that idiot Sal made of
my beloved Mac Automation, I hardly got squat. (To the few folks who did
file tickets: my sincere thanks for your time. Sorry we've not made
ourselves heard, but take that up with your peers.)
So 'scuse my toxic attitude nowadays, but it has been thoroughly earned.
Especially by the most experienced senior members of this community who
should be leading Automation to far greater achievements and massively
larger audiences, but instead are still running the same sad dog-n-pony
shows they were running when I first arrived, green as grass, seventeen
years ago. It impressed me then, it disgusts me now. Cos I've been
around the rest of the programming world, and seen what those other
communities can do, and if those assholes can build mighty (if stupid),
popular (if only to a self-selected audience) platforms like Python,
Ruby, et al, then why has the AppleScript community in 20 years
succeeded only in building nothing at all?
Oh, and I'm sure your sophisticated solutions are admirable for what
they are. But if you're looking to impress me, you'll find me and my
industry-expert collaborators over in the $1Tn global packaging world
for the next five years, carving ourselves a huge juicy chunk of the
artwork production market with *our* sophisticated solutions. Cos our
solutions aren't built by me, but by *us*. They might not like me either
(even I don't), but they sure as hell respect my work for what it
empowers them to do, just as I respect the hell out of them and theirs
for making it able to do it.
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