It is difficult to find an exact date for LISP’s birthday. It wasn’t so much born in an instant as it was gradually dragged out of the primordial slime during the heady days of late 50s computer research. What is known is that John McCarthy, LISP’s “father”, published a report in October 1958 about his new programming language aimed at providing artificial intelligence capabilities on the IBM 704 mainframe computer. That report, one of a series, was the first one to use the name LISP.

OOPSLA, a major annual conference on object-oriented programming, has decided to celebrate LISP’s 50th birthday on 20 October 2008. Practically everyone at that event is likely to be smarter, geekier and possibly even more pedantic than me. So for now I’m going to go with that date and raise a glass to LISP and John McCarthy in one week’s time.

John Walker’s almost-accidental but still inspired decision to add LISP to AutoCAD was, in my opinion, the most significant feature addition in AutoCAD’s history. There were many other feature additions without which AutoCAD would be a joke (e.g. blocks, undo/redo, dimensioning, polylines) but they were always going to happen anyway.

Adding LISP wasn’t like that. It wasn’t inevitable. It was an excellent example of Walker thinking outside the box, and it was the one thing that raised AutoCAD significantly above its competitors (yes, it had serious competitors once) at a time when the PC CAD market was still up for grabs.

The genius of this move was that instead of attempting to fill AutoCAD’s many feature holes, Autodesk could provide the tools that would let the users do that for themselves. The language was an ideal fit for a number of reasons, and users in droves started hole-filling with a vengeance. Without that boost to AutoCAD’s open architecture, the PC CAD market would have been a very different place. Autodesk itself may not even have survived into the 1990s, and I could have been writing this blog about Versacad, Computervision, or some other competitor.

Today, despite an unfortunate history of long periods of neglect from Autodesk, LISP remains the language of choice for most of my AutoCAD-related programming needs. There are exceptions, but I’ll usually first see if a given job can be done in LISP. If it can’t be done easily and well in LISP, then I will consider using one of the other available languages. For the sort of work I usually do, that doesn’t happen very often.

Why? I’ll explain my reasoning in a later post.

I have been thoroughly enjoying Kean Walmsley’s interview of Autodesk co-founder John Walker, which he has now finished. Kean’s link to part 4 is currently broken (edit: now fixed) and that broken link has been picked up by others (edit: also fixed in Between The Lines), so here are the correct links: Part 1, Part 2, Part 3 and Part 4.

One of the best things about the interview is that it contains some frank criticism of Autodesk (and Microsoft, for that matter). On an Autodesk blog. Think about that. OK, it may be criticism of some stuff that is now ancient history, and it was made by someone who isn’t actually an Autodesk employee any more, but when was the last time you saw even that? It’s refreshing to see just a tiny crack appear in the never-say-anything-negative Autodesk facade.

I remember a time when Autodesk people were allowed to speak reasonably freely in public, often did so, and were even known to make admissions that not everything always smells of roses. John’s fellow Autodesk founder Duff Kurland once wrote this wonderful, wonderful response to a question of mine on the CompuServe ACAD forum (it was about Autodesk removing Visual Basic support without warning, if you’re curious):

We screwed up. We screwed up twice.

He then went on to explain the detail of how and why Autodesk had screwed up and exactly what they had learned from the experience. Can you imagine any Autodesk person saying that now? If they did, can you imagine that person remaining an Autodesk employee afterwards in anything other than a sweeping-up capacity? Nor me, and that’s a real shame. It would be easy enough to justify it by saying Autodesk is a public company and has a glossy corporate image to preserve, but nevertheless it’s still a real shame.

Back to John Walker. Although John has been away from the AutoCAD scene for an age now, I’ve still been enjoying his comments for many years in The Autodesk File, which I’ve always said should be compulsory reading for all new Autodesk employees. I haven’t always agreed with John’s views on everything, but they are intelligently presented, sometimes confronting, and often entertaining. Besides, it’s hard for me to argue with somebody who has succeeded in the way he has; he could always say, “Well, I did this. What have you done?”

Here are some of my favourite John Walker quotes (from The Autodesk File):

If we continue, as we have done consistently for the last eight years to measure every proposal against the standard, “How does this benefit the customer?”, I believe the success we’ve experienced to date will be just the base upon which far greater achievements can be built.

…we must never forget our customers. It is the customer, ultimately, that we are working for, and it is the customer who we must always strive to satisfy. All the rest will take care of itself, in the fullness of time.

Around here, I’ve been known to say things like, “I don’t care what you think. What do the customers think?”. That may sound arrogant, but to me it’s just plain old common sense. The evidence that it works is all around us.

Finally, and if you’re trying to lose weight, have a read of John’s The Hacker’s Diet. It’s also common sense and my slowly shrinking gut is evidence that it works.

I have a lot of posts about AutoCAD and a few about grammar, but I expect this will be the only post I ever make that combines the subjects.

Autodesk founder John Walker, a very prominent figure in AutoCAD’s history, has written an article about the correct use of the apostrophe. While I enjoyed it, I think it’s too insulting to be useful. People struggling with the correct use of the apostrophe are unlikely to get past the part where they are called morons, to read the useful advice below.

If you just want simple apostrophe advice without being belittled, I suggest you look at the main page of the The Apostrophe Protection Society instead.