[zzygan]

This must have come out of the ITA Software acquisition.... (Heading "Attention required" 'You must follow the ITA convention of using...') They were a big common lisp user apparently.

Google is normally very specific on the languages allowed for internal projects. A product/company acquisition with large assets written in common lisp would necessitate this becoming the "Google Common lisp style guide" rather than what it was most likely originally the "ITA Software" common lisp style guide. Speculation of course, but looks likely.

[hollerith]

>This must have come out of the ITA Software acquisition

One of the authors, the one that goes by the name Faré, definitely came with the ITA acquisition.

[geofft]

ITA continues to be heavy users of Common Lisp.

[mck-]

Do you know this for a fact? That'd be quite impressive if the Lispers maintained strong against Google's policies.. I remember reading that they ported over

[dmbaggett]

I oversaw development at ITA for many years and can tell you the probability that they're going to port QPX to Java is nil. (Or perhaps NIL.)

[nandemo]

On the contrary, it would be impressive if Google managed to make them port half (or more of) their codebase from Lisp to Java and still keep the ITA employees, some of whom are hardcore lispers.

[7rurl]

I have a friend who works for ITA/Google today, and he tells me they are still using Lisp and their Lisp codebase is huge and complicated and not likely to ever be ported to another language.

[mck-]

That's awesome -- so with them publishing this style guide, are they trying to reach out to the Lisp community for recruitment purposes?

[rbanffy]

Lispers tend to be a clever bunch. I'm quite sure they can be very convincing.

[Evbn]

ITA has been writing Java for almost 10 years for their website.