• 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: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)


  • Subject: Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
  • From: has <email@hidden>
  • Date: Wed, 17 Dec 2008 20:39:31 +0000

Shane Stanley wrote:

On 17/12/08 10:44 AM, "Chris Page" <email@hidden> wrote:

I think it's best to avoid using unnecessary tell blocks.

But here is part of the problem. You have a language that tries to appeal to
neophytes. It was designed so that things like nested tells and calling
scripting additions within tell blocks Just Worked -- and then you say oh
yes, but please don't do it. You're putting the onus for avoiding any
problems it might cause on the wrong person, IMO.


Agreed. There's no point being precious about such things, because neither AppleScript nor AppleScript users care if code is aesthetically pleasing or academically correct as long as it runs and does [more or less] what they want.

This is why I think adding namespaces for osaxen isn't justified, even though they're the right thing to do in terms of good language design. [1] The great mass of AppleScripters couldn't care less for their academic merits, and while the lack of namespaces does occasionally cause practical problems that do affect users, changing the current behaviour would affect them a whole lot more. The current behaviour may be technically flawed, but it's what users and their scripts have learned to expect.

Regards,

has

[1] In contrast, the reason I advocate changing the way that osax commands are handled is because the current behaviour affects not just AppleScript but the entire system, and AppleScript's personal convenience should never justify risking Mac OS X's overall integrity. (Those who still feel otherwise would do well to look at Microsoft, who have spent the last decade trying to undo the damage they caused by putting some users' every demand for short-term convenience before all users' permanent safety.)

--
Control AppleScriptable applications from Python, Ruby and ObjC:
http://appscript.sourceforge.net

_______________________________________________
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: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
      • From: Chris Page <email@hidden>
    • Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
      • From: "John C. Welch" <email@hidden>
  • Prev by Date: Re: on blocking target applications' GUIs (was Re: Tell Blocks Considered Harmful)
  • Next by Date: ersatz list-mom moment (was Re: Tell Blocks Considered Harmful)
  • Previous by thread: Re: on blocking target applications' GUIs (was Re: Tell Blocks Considered Harmful)
  • Next by thread: Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
  • Index(es):
    • Date
    • Thread