Ancestors

Written by SyntaxError :sdf: on 2024-11-13 at 00:12

Question for lispers with experience: If you should start to learn a LISP style language today, which one do you pick up? Why?

[#]lisp #scheme #commonlisp #programming #lispers #developers

=> More informations about this toot | More toots from syntaxerror@mastodon.sdf.org

Written by Daniel Lakeland on 2024-11-13 at 00:24

@syntaxerror

I know it might not seem like it but #julialang is secretly a LISP. That's what I'd recommend these days.

=> More informations about this toot | More toots from dlakelan@mastodon.sdf.org

Written by Chris L on 2024-11-13 at 00:27

@dlakelan @syntaxerror first class lambdas with lexical closure or reader macros or regular macros?

=> More informations about this toot | More toots from jayalane@mastodon.online

Written by Daniel Lakeland on 2024-11-13 at 00:33

@jayalane

First class lambdas with lexical closures. String conversion macros (basically you can write your own parser for strings that produces syntax tree). And regular macros.

@syntaxerror

=> More informations about this toot | More toots from dlakelan@mastodon.sdf.org

Written by Chris L on 2024-11-13 at 00:46

@dlakelan @syntaxerror well I am impressed. I am learning matlab which is kind of cursed and have been tempted by Juliablog articles.

=> More informations about this toot | More toots from jayalane@mastodon.online

Toot

Written by Daniel Lakeland on 2024-11-13 at 00:57

@jayalane

Common LISP was an explicit inspiration for Julia, as was Matlab syntax (for math, but not similar semantics). And it compiles to native code and most of Julia is implemented in Julia. Used to be the parser was in scheme but they've moved to JuliaSyntax package as the parser recently.

@syntaxerror

=> More informations about this toot | More toots from dlakelan@mastodon.sdf.org

Descendants