On Fri, Oct 14, 2005 at 02:36:29PM -0400, Roger Merchberger wrote:
Rumor has it that Chuck Guzis may have mentioned these
words:
Suppose you wanted to write an application for a
manufacturing process that
will, in all probability, run for the next 30 years...
What would you write it in?
If for some inane reason, Forth isn't a contender, then I'd pick Perl
4.0.x. It's stable, still being used, and runs on equipment as old as an
Atari ST. And, I *think* it's ontopic. If not, it's really close.
I'd not pick perl 4. It's not being maintained. You have to assume
that the hardware running the program may need replacing, and that an
identical replacement may not be available. And then you'll find that
it no longer builds on any new hardware/OS/compiler you can buy.
I'd go for strictly ANSI-standard C, on some species of toughened,
sealed PC.
That said, I've been maintaining a computer and program used for running
a small business's production equipment (boilers and stuff for making
aromatherapy oils) for the past 13 years. I wrote the program in Z80
assembler, and it runs under CP/M on an Amstrad CPC. Every year, I've
gone there, blown the dust bunnies out of the drive, a couple of times
I've replaced the drive belt, once I had to re-solder the video
connector and once I used some silver paint to fix a broken trace on the
keyboard wossname. But after I do the routine checks and maintenance
this year, I'm going to tell the guy that he's renewing the maintenance
agreement for the last time. Yes, it's easy money, and I could do it for
at least another two or three years before I can no longer trust my
spare drive belts, but it would be easier for me if he just moved to
something a bit more modern. My maintenance fees would be higher too,
given that modern hardware is not so easily repairable :-)
--
David Cantrell | London Perl Mongers Deputy Chief Heretic
Nuke a disabled unborn gay baby whale for JESUS!