By the time I got it, most of it was calls to Win32 functions, and almost nothing was using any functionality Autohotkey was any good at. I didn't even dare talk about it on the Autohotkey fora at the time, because I was sure the developers themselves would consider me an insane idiot and/or hit me with an axe. I migrated it to another language the day I understood it well enough.
One of the great truths of ICT is: Anything can survive production if someone decides to bless it with insane amounts of time and money.
But Common Lisp is not the language to use in production (at least in a larger commercial context!) if your primary need is CRUD or glue. It does fine at those things, but Lisp is better wielded at problems that require "power in the large", like building a new compiler, solver, simulator, or "engine" of some sort, for instance. For those, the programming language matters a lot more than the libraries, in my opinion.
I've had no issue using Common Lisp in production and employing teams to write and maintain it.
To compare, this is what a psuedo-popular-lang might look like:
let year = parse-integer(string, start=0, end=4)
let month = parse-integer(string, start=7, end=7)
let day = parse-integer(string, start=9, end=10)
return ((year * 31556926 + ;; no. of seconds in a year
month * 2629743 + ;; no. of seconds in a month
day * 86400) - ;; no. of seconds in a day
1900 * 31556926) ;; lisp timestamps start at 1900
Honestly that looks pretty run-of-the-mill to me.Having said that, rolling your own date logic is insanity, as the problem is difficult[1] yet solved[2].
[1] https://gist.github.com/timvisee/fcda9bbdff88d45cc9061606b4b... [2] https://common-lisp.net/project/local-time/manual.html
Well, I don't see any difference with any other language you could use, from SQL, to C ,CSS or JSON.
The fact is that the higher your corpo overlord, the less is he going to understand your scrawl.
Instead of them understanding your language, it is you who need to speak theirs. You will need to understand MBA talk in order to communicate in simple terms(elevator pitch) why you using this weird language is important for the company.
Then they will leave you alone if what you promised is true, or just fire you if it is not.
Your senior software engineering colleague who is a huge "Python is the second best at everything" fan will be more of a hindrance than your boss, typically. It's not wholly invalid, but it can easily become a social/political issue rather than a technical one. If someone else is proposing a popular approach (like building a backend in Python), and you're proposing an oddball one (like using Lisp), be prepared for their solution to start off with 50 points of consensus and yours zero.
(This goes for many other languages too. C, JavaScript, Java, Haskell, R, Perl -- they all have their "holes" in the standard library that need to be filled in.)
Not only they are the survivors, they also come with additional libraries for all kind of stuff not covered by the standard.
This is part of the rationale behind Clojure, being able to lean on established platforms (Java and later JS): https://clojure.org/about/rationale
With that said, though, that parsing function doesn't seem all that complicated?
This is a big reason for the Rhombus project in Racket[1] one of it’s main goals is to be a Lisp like language which combines the extensibility of a parens based language, with infix notation and a different surface syntax
But then I see a code snippet, something like this manual datetime string parser. Apparently the programmer needed to roll their own, and I wonder: how on earth am I going to convince my corpo overlords that this language belongs anywhere near a production system?