comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Introducing FL
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Introducing FL [message #48266 is a reply to message #48144] Mon, 03 April 2006 19:17 Go to previous messageGo to previous message
Craig Markwardt is currently offline  Craig Markwardt
Messages: 1869
Registered: November 1996
Senior Member
JD Smith <jdsmith@as.arizona.edu> writes:
>> And finally, with this proliferation of "almost-IDL" clones (FL, IDL,
>> ANA, Yorick), I have to wonder why everybody has to re-invent the
>> wheel (see above). I see the GDL people meticulously toiling over
>> basic functionality, and it makes me wonder: wouldn't it have been
>> better to write an IDL-to-{Python,Ruby,Perl} translator, and get the
>> existing well tested script environment for free? And not only that,
>> but Python for science seem about to really take off. An infusion of
>> well-tested IDL libraries into that community might be enough
>> cross-fertilization to really get a non-proprietary version of an
>> IDL-like language going strong.
>
> Python has been set to "take off" in the astronomy field for about 8
> years, and it just hasn't really happened. In my view, it's just
> inertia. It took RSI 30 years to get to where they are, and they have
> built up an impressively large (if ungainly and not exactly stylish)
> bag of tricks.
> ...

True, but that's kind of my point. *If* we could easily translate all
our IDL code to Python (say), we'd have the immediate benefit of a
stable and supported runtime environment, where the wheel had already
been invented, and done well.

Then there are all sorts of possibilities. An individual could then
(a) translate all of their routines to Python and then just "switch"
to Python once and for all. Or (b) they could still think in IDL but
compile to Python whenever needed.

Python would gain a whole suite of great science software originally
written for IDL, and IDL users would gain the freedom to switch away
from a proprietary environment. Everybody would gain! (with very
little change in inertia)

I just don't think it's possible for the clone writers of GDL or FL
can sustain the effort long enough to write a complete new invention
of the wheel (interpretter environment plus library). [*] Why not let
the Python people do more than half of that?

Craig

[*] - I do appreciate the impressive effort that the GDL and FL
writers have put in!

--
------------------------------------------------------------ --------------
Craig B. Markwardt, Ph.D. EMAIL: craigmnet@REMOVEcow.physics.wisc.edu
Astrophysics, IDL, Finance, Derivatives | Remove "net" for better response
------------------------------------------------------------ --------------
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: iTools/interactive Analysis >
Next Topic: Anything in IDL like R's Copy to Clipboard As a Metafile?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 17:52:08 PDT 2025

Total time taken to generate the page: 0.00429 seconds