2,368 karma · joined May 18, 2017
Yes.
However, the 99.9999% of Julia code out there isn't in s-expressions. Every Julia programmer doesn't use s-expressions. They use Julia syntax.
Thus, the task of writing Macros in Julia is harder than doing the same thing in Lisp.
>So I'm seeing nothing that would be problematic if it had just gone with a Lisp syntax.
They should've gone with a Lisp syntax, IMO. Beginners, who haven't passed through the chore of learning C-like syntax, find s-expressions as easy as any other kind of syntax.
This pretty much disqualifies it as a functional programming language.
Additionally, Guido and the community in general discourage functional programming. While the Common Lisp community already has a lot of libraries for FP, like FSET and others.
Only if your knowledge of Common Lisp is at the level of "armchair specialist".
Substantiate your claims.
I didn't know that having leaky abstractions on top of the horrible Java standard lib was "being closer to math"
>The AIMA/PAIP code in Common Lisp, for instance, are ugly as hell
perhaps it just means you are familiar with python, not lisp.
I have 3 years of experience with both and let me tell you, there is nothing elegant in Python: there's nothing elegant in having to deal with one-line lambdas, global interpreter lock, 30x-50x longer execution times than Lisp, distinction between statements vs expressions, mutability everywhere, a flaccid OOP system, no interactive development features, and horribly written libraries.
However Common Lisp is a lisp-n, it has at least 5 namespaces: functions, symbols, keywords, classes, signals, packages...
What are methods and classes in a language like Java? Those are "roll your own constructs" as well.
In lisp code you can define your own functions and macros, yet the end still looks like lisp code.
That's FUD. Just make your code modular. Lisp gives you tools: namespaces, and systems.
>You can at least count on functions not having side-effects.
The great majority of functions in Lisp don't mutate data.
Common Lisp more than compensates due to some key features:
1. any bug can be corrected at runtime without having to stop the program
2. the type system is completely strong, not weak
3. it actually has a pretty nice type system.
4. the conditions-restart exception handling system is world-class
And Unix is what happened when Bell Labs wrote an operating system -- something that was born outdated from the start.
Just like Golang.
Common Lisp has been used in scientific computing since decades, so in some sense it's "ready". Also, see CLASP: lisp at the state of the art of computational chemistry.
Yes, and this is practically the only thing that I find wrong with Julia, besides the lack of the interactivity of CL.
It's like populism -- an inferior syntax choice taken just to attract the Pythonistas.
You won't, since Lisp editors automatically keep parentheses balanced.
This is a myth perpetuated by people with zero lisp experience.
I've navigated plenty of lisp libraries' codebases and haven't found not a single case of that.
>I've heard this called "the curse of Lisp
An essay written by... a graphic designer with zero Lisp experience.
I do.
Lisp stopped being slow a long, long time ago.
Armed Bear Common Lisp is an ANSI Common Lisp, thus can use all CL libs, runs on the JVM, and it can easily call Java libraries. In fact as easy as calling regular lisp functions.
Do you want your kid to learn actual computer science, or do you want him/her to basically be able to create a cookie cutter mobile app?
Logo is a bare-bones Lisp disguised as an educational language.
There's no God.
I've good news for you: Lisp is an imperative language.
No, they aren't. They are the same as languages from 40 years ago: We have had channels, coroutines, and good garbage collectors from long, long ago. Plus the syntax is directly borrowed from Algol 68 (from 1968).
Go looks nice because it fills a niche (a high performance garbage collected language that is easier to learn than Java and provides faster compilation times than C++), but there's absolutely nothing different here.
For "pretty different from mainstream" see Forth, Prolog, Erlang, etc.
I value simplicity, that's what i use Brainfuck. Far simpler than Go and Zig.