Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #84459

Re: What killed Smalltalk could kill Python

From Gene Heskett <gheskett@wdtv.com>
Subject Re: What killed Smalltalk could kill Python
Date 2015-01-24 06:34 -0500
References <54bfd513$0$12978$c3e8da3$5496439d@news.astraweb.com> <mailman.18065.1422053606.18130.python-list@python.org> <cih2afF6b1mU1@mid.individual.net>
Newsgroups comp.lang.python
Message-ID <mailman.18082.1422099271.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Saturday 24 January 2015 03:09:51 Bob Martin did opine
And Gene did reply:
> in 734904 20150123 225104 Tim Daneliuk <tundra@tundraware.com> wrote:
> >On 01/21/2015 05:55 PM, Chris Angelico wrote:
> >> On Thu, Jan 22, 2015 at 10:37 AM, Tim Daneliuk 
<tundra@tundraware.com> wrote:
> >>> I find these kinds of discussions sort of silly.  Once there is a
> >>> critical mass of installed base, no language EVER dies.
> >> 
> >> Not sure about that. Back in the 1990s, I wrote most of my code in
> >> REXX, either command-line or using a GUI toolkit like VX-REXX.
> >> Where's REXX today? Well, let's see. It's still the native-ish
> >> language of OS/2. Where's OS/2 today? Left behind. REXX has no
> >> Unicode support (it does, however, support DBCS - useful, no?), no
> >> inbuilt networking support (there are third-party TCP/IP socket
> >> libraries for OS/2 REXX, but I don't know that other REXX
> >> implementations have socket services; and that's just basic BSD
> >> sockets, no higher-level protocol handling at all), etc, etc. Sure,
> >> it's not technically dead... but is anyone developing the language
> >> further? I don't think so. Is new REXX code being written? Not a
> >> lot. Yet when OS/2 was more popular, REXX definitely had its
> >> installed base. It was the one obvious scripting language for any
> >> OS/2 program. Languages can definitely die, or at least be so left
> >> behind that they may as well be dead.
> >> 
> >> ChrisA
> >
> >Rexx is still well used on mainframes.
> 
> http://www.oorexx.org/
> 
> I use ooRexx every day, on Linux mostly, but also available on Windows.

Can it run typical AREXX source?  I don't see a single syllable on that 
now 5 year old site indicating any such capability.

Example: Something needs to be synchronized to occur in the first tick of 
the next minute, and has nothing to do until then, so it queries the 
system for the number of ticks remaining in this minute, then puts itself 
to sleep for that long.

Is this possible in ooRexx?

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

What killed Smalltalk could kill Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-01-22 03:34 +1100
  Re: What killed Smalltalk could kill Python Michiel Overtoom <motoom@xs4all.nl> - 2015-01-21 18:45 +0100
  Re: What killed Smalltalk could kill Python Tim Chase <python.list@tim.thechases.com> - 2015-01-21 12:21 -0600
    Re: What killed Smalltalk could kill Python albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-02-07 23:35 +0000
  Re: What killed Smalltalk could kill Python Grant Edwards <invalid@invalid.invalid> - 2015-01-21 19:18 +0000
    Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-01-22 09:35 +1100
      Re: What killed Smalltalk could kill Python Grant Edwards <invalid@invalid.invalid> - 2015-01-21 23:10 +0000
        Re: What killed Smalltalk could kill Python Marko Rauhamaa <marko@pacujo.net> - 2015-01-22 02:25 +0200
        Re: What killed Smalltalk could kill Python Tim Chase <python.list@tim.thechases.com> - 2015-01-21 21:22 -0600
          Re: What killed Smalltalk could kill Python Grant Edwards <invalid@invalid.invalid> - 2015-01-22 17:52 +0000
    Re: What killed Smalltalk could kill Python Anthony Papillion <anthony@cajuntechie.org> - 2015-01-21 17:19 -0600
    Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-01-22 10:41 +1100
    Re: What killed Smalltalk could kill Python John Ladasky <john_ladasky@sbcglobal.net> - 2015-01-21 16:22 -0800
  Re: What killed Smalltalk could kill Python Tim Daneliuk <tundra@tundraware.com> - 2015-01-21 17:37 -0600
    Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-01-22 10:55 +1100
      Re: What killed Smalltalk could kill Python Tim Daneliuk <tundra@tundraware.com> - 2015-01-23 16:51 -0600
        Re: What killed Smalltalk could kill Python Bob Martin <bob.martin@excite.com> - 2015-01-24 08:09 +0000
          Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-01-24 19:16 +1100
            Re: What killed Smalltalk could kill Python Bob Martin <bob.martin@excite.com> - 2015-01-24 14:09 +0000
          Re: What killed Smalltalk could kill Python Gene Heskett <gheskett@wdtv.com> - 2015-01-24 06:34 -0500
            Re: What killed Smalltalk could kill Python Bob Martin <bob.martin@excite.com> - 2015-01-24 14:14 +0000
      Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-01-24 09:57 +1100
        Re: What killed Smalltalk could kill Python Tim Daneliuk <tundra@tundraware.com> - 2015-01-26 14:18 -0600
      Re: What killed Smalltalk could kill Python Tim Daneliuk <tundra@tundraware.com> - 2015-01-23 16:51 -0600
    Re: What killed Smalltalk could kill Python Michael Torrie <torriem@gmail.com> - 2015-01-21 17:08 -0700
    Re: What killed Smalltalk could kill Python Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-01-21 21:59 -0500
    Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-01-22 14:08 +1100
    Re: What killed Smalltalk could kill Python Emil Oppeln-Bronikowski <emil@fuse.pl> - 2015-01-22 05:46 +0100
    Re: What killed Smalltalk could kill Python Ethan Furman <ethan@stoneleaf.us> - 2015-02-09 13:28 -0800
  Re: What killed Smalltalk could kill Python Paul Rubin <no.email@nospam.invalid> - 2015-01-21 15:46 -0800
    Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-01-22 10:57 +1100
      Re: What killed Smalltalk could kill Python Mario Figueiredo <marfig@gmail.com> - 2015-01-22 01:09 +0100
        Re: What killed Smalltalk could kill Python sohcahtoa82@gmail.com - 2015-01-21 17:00 -0800
        Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-01-22 12:36 +1100
        Re: What killed Smalltalk could kill Python Paul Rubin <no.email@nospam.invalid> - 2015-01-21 17:38 -0800
          Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-01-22 12:45 +1100
            Re: What killed Smalltalk could kill Python Paul Rubin <no.email@nospam.invalid> - 2015-01-21 18:53 -0800
              Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-01-22 13:59 +1100
                Re: What killed Smalltalk could kill Python albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-02-07 23:54 +0000
                Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-02-08 11:57 +1100
                Re: What killed Smalltalk could kill Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-02-08 18:59 +1100
                Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-02-08 19:24 +1100
            Re: What killed Smalltalk could kill Python alex23 <wuwei23@gmail.com> - 2015-01-23 15:35 +1000
              Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-01-23 17:07 +1100
        Re: What killed Smalltalk could kill Python Ethan Furman <ethan@stoneleaf.us> - 2015-01-21 17:44 -0800
        Re: What killed Smalltalk could kill Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-01-22 14:23 +1100
          Re: What killed Smalltalk could kill Python Chris Angelico <rosuav@gmail.com> - 2015-01-22 15:34 +1100
          Re: What killed Smalltalk could kill Python alex23 <wuwei23@gmail.com> - 2015-01-23 15:39 +1000
            Re: What killed Smalltalk could kill Python sohcahtoa82@gmail.com - 2015-01-23 14:48 -0800
              Re: What killed Smalltalk could kill Python Emile van Sebille <emile@fenx.com> - 2015-01-23 14:58 -0800
    Re: What killed Smalltalk could kill Python Mario Figueiredo <marfig@gmail.com> - 2015-01-22 01:16 +0100
      Re: What killed Smalltalk could kill Python Terry Reedy <tjreedy@udel.edu> - 2015-01-22 00:45 -0500
  Re: What killed Smalltalk could kill Python Rick Johnson <rantingrickjohnson@gmail.com> - 2015-01-21 18:11 -0800
    Re: What killed Smalltalk could kill Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-01-22 06:30 +0000
  Re: What killed Smalltalk could kill Python Gene Heskett <gheskett@wdtv.com> - 2015-01-22 07:26 -0500
  Re: What killed Smalltalk could kill Python Emil Oppeln-Bronikowski <emil@fuse.pl> - 2015-01-22 16:47 +0100
  Re: What killed Smalltalk could kill Python Tony the Tiger <tony@tiger.invalid> - 2015-01-23 18:04 +0000

csiph-web