[ruby-talk:01430] Re: Scripting versus programming

Hi,

In message "[ruby-talk:01376] Re: Scripting versus programming"
    on 00/02/15, Andrew Hunt <[e-mail]> writes:
|
|Conrad writes:
|
|    >I recommend that we (and Ruby documentation) describe Ruby first and
|    >foremost as "one of the world's most powerful programming languages", and
|    >subsequently mention that is also enormously useful for scripting--if, when,
|    >and where appropriate. This may (or probably should) sound trite to
|    >technically astute people, many business/IT decisions at tens of thousands
|    >of shops world-wide are unfortunately made on the basis of superficial
|    >impressions.
|
|I agree whole-heartedly!
|
|I think it is misleading to call Ruby a scripting language, and
|the unelightened might mistake it for another VB or Perl, or
|even a replacement for JavaScript.

Well, I mean the followings by the word `scripting':

  * interpretive
  * easy to program
  * very high level language
  * prenty of features to manipulate files and strings
  * language for the future, according Ousterhout

all of these attributes are covered and targeted by Ruby.
But in case you feel `scripting' bothers, you can call it whatever.

							matz.