3 ms·
I have recently blogged that AI and Common Lisp don't mix, but I've come to the opposite conclusion lately. AI evens the playing field between large teams and s
by djha-skin 6mo ago
I have recently blogged that AI and Common Lisp don't mix, but I've come to the opposite conclusion lately. AI evens the playing field between large teams and single developers. Now all the lone wolves in cl will be able to do large things, like a .net implementation or a yaml parser. I heard one guy say he was using AI to write a c complete in common lisp. I wonder if AI was used here or not.
- pjmlp 6mo agoHad it not been for UNIX taking over the Lisp workstations market, followed by the first AI winter, people would be using LispTorch today, and there wouldn't have been such a waste coming up with endless ways to speed up Python, and efforts like Mojo wouldn't even be a thing.
- Pay08 6mo agoNot really the "fault" of UNIX. The Lisp workstations would have been just as unpopular without it. They were insanely expensive and the idea of a workstation was ahead of its time, not to mention the other "unneeded" extras like GUIs, a mouse, and the photo editing and 3D modelling suites. It was plainly uneconomical.
- pjmlp 6mo agoUNIX was only cheap because AT&T was forbidden to profit from it, had it not been the case, it would have been a proprietary closed source OS, exactly at similar price points. The proof being the graphical UNIX workstations from Cray, SGI, Sun, NeXT that came later into the market.
- Pay08 6mo agoThe dimension you're missing here is that most of the Lisp OSs were single-user (AFAIK initially all of them were but some gained multi-user support later) in a period when timeshare was king. Not to mention that the hardware itself cost multiple times more to manufacture.
- pjmlp 6mo agoHow many UNIX graphical workstations from Cray, SGI, Sun, NeXT do you think were multiuser in practice? As for price, they were also not cheap to get.
- jrumbut 6mo agoYou could probably say the same about any operating system, especially if you exclude the same human user operating in multiple roles. Though in the Unix environment, additional user accounts and groups that don't actually correspond to separate humans have a lot of pragmatic uses.
- pjmlp 6mo agoYes, however that wasn't a relevant feature for 1980-90's workstation market, like under which user the printer daemon would be running under.
- jksmith 6mo agoUse python or whatever to build the llm, use lisp to explore and infer from the edges of what the llm has to offer. I don't do anything but lisp these days. Been waiting my whole career to be at this point. I'll never "write" a line of C# again. Just my taste and pref.
- jjtheblunt 6mo agomay i ask which lisp variant you are using?
- jksmith 6mo agoFranz Allegro toolchain.
- jjtheblunt 6mo agoIs it preferable to Lispworks?
- jksmith 6mo agoI personally don't know anything about LispWorks except for the name. My pref for Franz is the commercial quality and the toolchain. If you have forgotten your graph fundamentals, Allegro Graph will make you want to get back into it. Very powerful tool for proofs and modeling the world.
- jjtheblunt 6mo agomakes sense. i have kept a valid mathematica license since the dawn of mathematica time (1988) for such trickery.
- arikrahman 6mo agoLikewise, I would never have thought to be daily driving Elisp on Emacs and Clojure in production, but here we are.