3 ms·
This is all false and misleading. Lisp is a language family, not any one language. There is no the Lisp, from which it follows that Lisp cannot be "THE language
by kazinator 6y ago
This is all false and misleading. Lisp is a language family, not any one language. There is no the Lisp, from which it follows that Lisp cannot be "THE language".
Are you saying that you can solve any problem with no impedance mismatch in AutoLisp?
- daly 6y agoFalse and misleading? The chosen languages have changed the way I've thought about programming. In my 'lived experience', Lisp is 'THE language' of thought. I'd welcome your choice of language and why you think it deeply affects the way you program. I've used 'lisp' since 1970, in a FORTRAN implementation of Lisp 1.5 out of Bell Labs. Clearly 'lisp' has evolved since that time. But all versions I've used, like MacLisp, Symbolics, Interlisp, Lisp/370, VMLISP, CCL/MCL, Portable Standard Lisp, KCL, AKCL (I'm a minor author), Emacs Lisp, CLISP, Lucid, Gold Hill, ABCL, Clojure, and a few others I've probably forgotten. They are all 'different' but all are recognizably 'lisp'. I don't know AutoLisp but I suspect that it might have the 'clay-like' property of other 'lisps'. The point of this series is to find languages that change the way you think. Don't confuse an implementation with the concepts.
- kazinator 6y agoIs this non-implementation language of thought documented somewhere, so that people can learn it and think with it? And does this language have mutable cons cells, with lists terminated by nil, which is a self-evaluating symbol that also denotes false? Are there interned symbols, quote and all that?
- martyalain 6y agoHi kazinator, are you replying to "daly" or to "martyalain"? If it is to me and about lambdatalk, some answer can be found in the links given previously.
- daly 6y agoAssuming you're not trying to be sarcastic... As a "language of thought" it is often the case that I will write my solution in Lisp and then "hand translate" it to the target language. This has two effects. First, assume I'm "translating" to Python, for example. The Lisp "Gedanken" keeps me from depending on strange local language behavior. For example, I won't have to catch missing dictionary entries. But if I happen to want a local language behavior I can just make a macro. Second, the Lisp "Gedanken" allows the ability to "factor" solutions since Lisp tends to "encourage" functions. For example, I'm working on a design for a dependently-typed language that allows proofs of the resulting programs. Lisp allows me to create a domain-specific language easily. Gedanken experiments led me to factor the category, domain, and representation for the specification, implementation, and proof languages. I know from experience that whatever domain-specific language constructs I dream up, they can all be implemented as macros and compiled efficiently. When "thinking in Python", you'll find yourself restricted by implementation issues or searching for some library and then shaping your problem to fit the library. When "thinking in Java", you'll find yourself trying to force your solution into "objects". When "thinking in C++", you'll find that (a) you have to choose WHICH C++ (there are so many) and (b) by the time you implement something C++ will have changed. I can still run Lisp code I wrote in 1980. Assuming you ARE being sarcastic... there's Greenspun Tenth Rule: Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp The fact that you've immediately gone to "interned symbols" means you aren't used to using your language for thinking. These things don't arise in Lisp Gedanken. Cogito, ergo Lisp
- kazinator 6y agoThe thing is, if your language of thought doesn't have interned symbols, or conses, is it really Lisp? Does your language of thought at least have first/rest recursion on lists, and do you use those idioms? If you naively transliterate that to Python, that's not very performant or idiomatic; you can't work with Python people that way. Are you sure your language of thought is really Lisp? Actual programs in a sophisticated Lisp dialect can't easily be spun off into Python or Java, at least if they are effectively using that dialect. If you want to treat Python through Lisp glasses, you may be best off getting one of the Lisp-over-Python implementations and adapting to them. Over the past several years, I have written a working program in an actual Lisp dialect to try an idea, which I translated to Python (system requirement: not introducing anything new to a container). I had to backpedal from some nice idioms in that Lisp dialect, and adapt to the Pythonic way of doing things. Part of the reason for that was people: the script had to pass code reviews, as well as lint programs like pylint3 and flake8. > When "thinking in C++", you'll find that (a) you have to choose WHICH C++ (there are so many) and (b) by the time you implement something C++ will have changed. If you think in terms of C++98 through maybe C++2003, you're okay. Hipsters working with your code will moan and groan that there is no emplace, move semantics or lambda, but not that it doesn't work.
- martyalain 6y agoAs an architect I disliked Autocad and its scripting language, Autolisp which is the worse implementation of the Lisp way I know. It's when I discovered Scheme that I began to understand what the Lisp way could bring for me, as a non professional coder. And it's when I went down and analyzed its foundations, the lambda calculus, that I began to understand how a programming language can be built. In the past, as a teacher in CAD, I have been writing rather useful code with Ruby working in Sketchup3D, and I loved this language. But today, as a past architect with time enough to think quietly (until death) about a programming language, the Lips way is my way: http://lambdaway.free.fr/lambdawalks/?view=fromroots2canopy http://lambdaway.free.fr/lambdawalks/?view=fromroots2canopy The only problem I encountered in my trip to the world lisp ... came from some Lisp priests who do not accept any other vision of Lisp than their own. And end up putting anyone off. The only thing that matters is the pleasure one can take in elegantly coding beautiful algorithms. The rest is negligible, at least for me, who is nearing the end of my life. Best regards Alain Marty