in reply to Re^2: Spreadsheets, HTTP::Recorder and interactivity
in thread Spreadsheets, HTTP::Recorder and interactivity

You're not meditating on the topic. You're blasting a response as quick as you can type.

Excel is just a application, written in some language. That language could even be Perl, for all you know! It is simple to use and simple to extend. It was designed to be simple in the simple case and powerful in the complex case.

Perl is a language. IT IS NOT AN APPLICATION. People use programming languages when the existing applications are either too simple, too heavy, or otherwise unsuited for their needs.

Please meditate on why you are insisting on comparing apples and Porsches.

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested

  • Comment on Re^3: Spreadsheets, HTTP::Recorder and interactivity

Replies are listed 'Best First'.
Re^4: Spreadsheets, HTTP::Recorder and interactivity
by zby (Vicar) on Jul 01, 2004 at 15:25 UTC
    I use perl and Excel for data manipulation and I compare them as a tool for data manipulation.
      That's cool. Except, you made some very sweeping statements about programming in general. Maybe you should update your original post to make it clear that you are dealing specifically with the task of interactive data manipulation. At that point, I'll argue that Excel is a better tool than Perl could ever be ... because Excel is an application.

      You have to realize something - applications are meant to be used interactively. Programming languages are meant to be used without interaction. You're still comparing apples and Porsches.

      ------
      We are the carpenters and bricklayers of the Information Age.

      Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

      I shouldn't have to say this, but any code, unless otherwise stated, is untested

        But I am not dealing about specificialy interactive data manipulation, I am talking about data manipulation in general. I compare interactive data manipulation with programming as two ways to do data manipulation. So I compare interactivity with batch mode.
        You have to realize something - applications are meant to be used interactively. Programming languages are meant to be used without interaction.
        Once again I compare applications with programming as two ways to solve the same thing, the first one is interactive, the second one is batch mode. So it's all straw man here (and a bit rude in the wording I need to add).