• 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: AS Library Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AS Library Question


  • Subject: Re: AS Library Question
  • From: has <email@hidden>
  • Date: Sun, 13 Dec 2015 18:55:05 +0000

Shane Stanley wrote:

> On 13 Dec 2015, at 3:50 AM, has <email@hidden> wrote:
>
>> it's not as if other languages, e.g. Python and Ruby, don't have the same problem too
>
> I'll take that as agreement that the issue is not crippling after all. Glad we cleared that up.

Mate, you really should stick to "How To Script <Application/Cocoa>" discussions, because your apologetics work sucks.

The Python and Ruby interpreters, having Unix roots, were never designed to run in-process but as individual sub-processes, which is how Unix usually does things. (They were also built by amateurs, so their interpreters are riddled with global state and corresponding hackarounds, e.g. Python's GIL.) So they suck for the sort of embedded use that OSA supports, which is why you rarely see them used that way. (Why d'you think I junked all my work on a Python OSA component?)

Whereas AppleScript was *specifically designed* to run in-process, via OSA which is likewise *specifically designed* for in-process use. After 20 years of allowing developers free rein in how they implement attachability, the AS team unilaterally changed the rules from under them, which means that a whole bunch of attachable apps that used to work safely no longer can be trusted to do so.

..

Again, you *still* (intentionally?) miss the big picture: this absence of joined-up thinking, defensive coding, and real-world destruction testing is not a one-off slip: it's endemic throughout the Automation team's work. The odd screw-up, subsequently fixed, is utterly acceptable we're all human. An endless stream of them combined with absolute silence and point-blank refusal to acknowledge or address them, that is pure PEBKAC. If there's one thing I've learned (usually the embarrassing way) over the years, it's that you can't just blindly fanny around with a platform that thousands of other people are deeply critically reliant on - least of all just for your own amusement - because you *will* break their stuff. Platform developers MUST have a *duty of care*. e.g. Just ask Adobe CC automators about the last time Adobe broke their entire JavaScript support through their don't-give-a-crap carelessness.

Sorry if I harsh your buzz, but I'm one of the very few AppleScripters with both the technical knowledge and experience to point out that our Emperor is *constantly* in the scud, not only embarrassing himself but wrecking a platform we all know and (mostly) love, and which many of us totally depend on for our livelihoods too. If you don't think that's a problem, then tell us what we'll do if AppleScript dies? I can cite examples all day, but unless someone is going to pay me the big bucks to do all of the AS team's QA work for them then I have more productive things to do. Like kicking the crap out of my own code until it is fit for production. Or filing bugs on Swift, whose development team is absolutely adored by its users because they actually communicate and cooperate effectively, don't have a problem admitting when they made a mistake, and work their asses off to make their products the best they can be.

e.g. Here's the sort of thing Swift users are saying: <https://twitter.com/gte/status/675449964454158336>. You don't think I would LOVE to say the same about the AS team? You really don't understand me at all. The AS team are all lovely folks on a personal level, but their product and attitude sucks. I am a raging dick with a destructive attitude, but even people who can't stand my guts will tell you the product I've provided is, for _them_, the greatest thing since sliced bread. It's not about the individual, it's about the work, and how that work empowers - or screws - everyone else.


> Now you might answer Stan's question about your own software...

Sorry, I don't see it anywhere. If he could cc it to me directly I'll be happy to respond.

Regards,

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: AS Library Question
      • From: Chris Page <email@hidden>
    • Re: AS Library Question
      • From: Shane Stanley <email@hidden>
  • Prev by Date: Re: How to Run a "sudo" Terminal Command
  • Next by Date: Re: AS Library Question
  • Previous by thread: Re: AS Library Question
  • Next by thread: Re: AS Library Question
  • Index(es):
    • Date
    • Thread