• 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: AppleScript and shell scripting
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AppleScript and shell scripting


  • Subject: Re: AppleScript and shell scripting
  • From: "John C. Welch" <email@hidden>
  • Date: Mon, 30 Jul 2007 13:29:17 -0500
  • Thread-topic: AppleScript and shell scripting

On 7/30/07 10:00 AM, "Bill Briggs" <email@hidden> wrote:

>> It has nothing to do with "user friendly" whatsoever. Programming is never
>> really going to be that. What it has to do with is people accepting a
>> primitive toolset
>
>  So, what, exactly, is primitive about the toolset?  I'd say that lots of the
> tools have evolved over many years to be quite comprehensive and exceedingly
> capable. Give an example that shows what you consider "primitive" to mean.
> I've got a hunch it's kind of like the same pejorative as used in relation to
> "primitive" social groups.

Sure. I create a variable and load a text file into it, then modify that
variable via various commands, such as sed and do some other transformations
to the content via grep et al. I then save that variable out to another
file.

I want to watch that variable's contents every step of the way with no
additional statements required, rather like I can do now with Script
Debugger. Please, show me the shell script IDE that gives me SD - level
functionality and runs on Mac OS X.

>
>
>> and when the heretical idea is proposed that things
>> could, and indeed should be better, justifying the primitive toolset.
>
>  So maybe you should fallow has' advice and start the initiative to change it.
> Tell us how to "do it better" with the shell and maybe some of us will be
> motivated to make it happen.
>
>
>> It's a toolset issue nothing more. The current way of developing shell
>> hasn't changed appreciably in decades, and I don't see any technical reason
>> for it other than a host of "Well, that's just how we do things 'round here".
>> Bah.
>
>  Again, what is the nature of the "technical" fix that you'd apply? Seriously,
> if there's some vastly better way to do it, if you're not going to implement
> it, at least tell us what it is.

Bill, don't be obtuse just because you like the word. You're well aware of
the advantages of a modern IDE in development. I *can* do every AppleScript
I currently use in vi, but why would I bother when there are better tools
available. You *can* do everything at the command line, eventually, yet you
seem to enjoy a GUI. I'm talking about a modern IDE for shell. If I have to
explain that to you, then there's a conceptual disconnect that I've not the
time to overcome.

--
"The Mac OS X kernel should never panic because, when it does, it
seriously inconveniences the user."


 _______________________________________________
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: AppleScript and shell scripting
      • From: "Mark J. Reed" <email@hidden>
References: 
 >Re: AppleScript and shell scripting (From: Bill Briggs <email@hidden>)

  • Prev by Date: Re: AppleScript-Users Digest, Vol 4, Issue 357
  • Next by Date: Re: AppleScript and shell scripting
  • Previous by thread: Re: AppleScript and shell scripting
  • Next by thread: Re: AppleScript and shell scripting
  • Index(es):
    • Date
    • Thread