On Feb 26, 2009 I posted the following question in several social networks, and received enough encouragement to carry on:
I’m doing research on the history of APL which will eventually lead to a documentary film.
Does this interest you?
Why?
Now it’s July 2009, and I’m still keenly interested in hearing from folks in the APL, K & J communities…


The following comments were added to the IP Sharp Associates (IPSA) Alumni Association – LinkedIn Discussion:
Brian Oliver
Co-owner, APL Borealis Inc. and Computer Software Consultant
Lai Philip
Operatoins Expert
Robert Bernecky
Owner, Snake Island Research Inc and Computer Software Consultant
Richard Procter
Co-Owner, APL Borealis Inc. and Software Consultant
Don Wilkes
webmaster at Province of British Columbia
Mike Harrop
President, The Cottingham Group. IT Security, Strategies and Standards
Rob Hodgkinson (Sydney)
Director at RHO Invest Pty Limited
Catherine Lathwell
Independent Online Media Professional
KEVIN CLARKE
Software Developer at Thomson Reuters
Felix Pring
Owner, Felix Pring Limited and APL Software Consultant
Karl Walter Keirstead
President at Infinity/Civerex LLC
Rohan Jayasekera
Product Development Consultant for online products/services
Dan Brennan
Contract consultant specializing in Canadian Capital Markets processes and supporting technology
Morgan Smyth
President, Braegen Group Inc.
Tom Gibson
Customer value specialist
Mike Elbourne
Business Development Analyst at Thomson Reuters
Sam Sexton
Provisioning Team Leader at Thomson Reuters Ltd.
Joey Tuttle
Information Technology and Services Specialist and CEO, Tuttle Utility Gas, Inc.
Sandra Eadie
Independent Writing and Editing Professional
Allison Atkey
Owner of Atkey Consulting Inc.
New posts updated here – July 27, 2009
Garland Sharratt
BD, Prod Mktg/Mgt, Eng, Stds for High Tech
Sam Sexton
Provisioning Team Leader at Thomson Reuters Ltd.#
Rohan Jayasekera
Product Development Consultant for online products/services
Robert Bernecky
Owner, Snake Island Research Inc and Computer Software Consultant
Don Wilkes
webmaster at Province of British Columbia
Joey Tuttle
Information Technology and Services Specialist and CEO, Tuttle Utility Gas, Inc.
Catherine Lathwell
Independent Online Media Professional
Clement Kent
Ph. D. student at University of Toronto
Indira Mitra
Senior Business Consultant at BMO Financial Group
Indira Mitra
Senior Business Consultant at BMO Financial Group
David Greer Smith
Combining Words & Pictures with Purpose
Mike Vormittag
Senior Systems Analyst – Trading Systems at BMO Financial Group
Chris Andrews
Strategic-Thinking and Hands-On Consultant in Marketing, Product Management, Innovation
I’ll join other staff from the UK in expressing an interest. But if the program is about APL, you can’t really include stuff about IPSA and its company culture, UNLESS it turns out that in other companies involved in major use of APL, there was an interaction between the programming language and company culture that was similar. Which might well be true …
I’m a strong proponent of APL since 1981 when I wrote a near real-time multiplayer 3D (full screen using character graphics) game on an IBM mainframe and 3270 terminals that wowed the CS department. I went on to write multi-user finance and database applications in APL for a couple of years.
While working for Lotus on Lotus 123 and Symphony internals in assembler back in 1986, I began wishing I could create the types of financial applications I was able to create in APL, using Lotus 123 or Symphony macros and formulas, but that was just not possible. So, I began researching how to create an APL compiler and multi-user data exchange platform as a foundation to create more extensible and flexible multi-user office applications like spreadsheets and word processors that could be incorporated into vertical applications. I was familiar with the limitations of interpreted APL on mainframes and PC’s, which were more than just performance limitations, but key conceptual limitations of the implementations. I was a very capable assembly and C programmer by this time so I would write any performance critical code in C with inline assembly, so that was not the limitation of APL that bothered me. What I wanted was to be able to extend the definition of a workspace by extending how data and code were stored and represented such that it formed a user extensible, introspective platform. I also wanted to extend how the platform could share data and form a grid computing system.
The Simmunity research platform is the result of 20 years of research and 5 years of programming that implements an interactive, introspective APL compiler and grid distributed processing platform that operates just like an APL interpreter. It is designed to create Adobe Flash like interfaces and local processing capabilities on client PC’s and full server capabilities for crunching and sharing data.
I hope to release a publically accessible version of Simmunity in a year or two, but for now it is still an unreleased, Alpha level functionality project.
Well that is my APL story. Sometimes I wish I had chosen a simple language like BASIC to use as the platform foundation langauge for my office applications and verticals, because I might have been done with it already…
Hello,
I learned APL in 1974, from Dr. Patrick Haggerty, who single-handedly wrote the U of MD APL processor for the Sperry Univac 1100 Series mainframe computers. At the time, Sperry had nothing.
I was a part-time student programmer, and I was hired to maintain and enhance the APL interpreter. There weren’t many bugs, so I also maintained other software, but Dr. Haggerty had not yet implemented “scan” (“”), so he assigned that to me as a way of getting me involved in the interior of the interpreter, which was written in 1100 Series assembler.
Dr. Haggerty also wrote our “distape” package generator in APL, to make it easier to build our software distribution tapes, that we shipped out on request. This fairly large APL script would take, as input, a list of package names, and a mailing address. The “distape” script would generate and execute a list of commands that would cause one or more source tapes to be mounted (using operator console messages requesting certain tapes by number), files to be copied from them and onto the new “distape”. After all source files were copied, the script would verify the tape’s contents, and if successful, rewind, unmount it, and them produce a shipping label with the destination address.
The script was a demonstration that APL was a “real” systems language that could be used to not only perform all kinds of analysis on vectors and matrices, but could also be used to accomplish almost any kind of system activity.
The only downside to this script was that only a few of us staff knew enough APL to maintain it, so when Dr. Haggerty left the Computer Science Center, it wasn’t long before that script was replaced with a “modern” replacement, written in a macro language.
I still find APL and its descendants (A+, j, k, q) fascinating. J in particular seems very powerful, with forks, and hooks, and there is a quasi-object-oriented convention using locales, but I’m not quite as happy programming in J as I am in Ruby, and, increasingly, I find myself pondering why this is so.
From the LinkedIn Group APL – A Programming Language
Curtis A. Jones
Lecturer at San Jose State University
Devon McCormick
Senior QA for Quant Analytics at Standard & Poor’s
From the LinkedIn Group Iversonians
J. Merrill
APL and .Net guru
Hal Feinstein
engineer at a company
Stephen Taylor
Principal at Lambent Technology
Jan Karman
Independent Financial Services Professional
Curtis A. Jones
Lecturer at San Jose State University
I was the first woman to work in communications department with roger barnacle and jim field david chivers and fred perkins jim oxer died in a plane crash he had his own small plane. i have a photo of him and roger at to office party. http://www.ukopr great idea. V8 by the case load.