Hmmm that's too bad, I'd like a python-flavoured lisp. That is a relatively fast functional language that replaces most of the brackets with indentation.

Any suggestions?

> ... a relatively fast functional language that replaces most of the brackets with indentation.

You might like sweet expressions coupled with a common lisp, a scheme or racket:

http://readable.sourceforge.net/

http://docs.racket-lang.org/sweet/index.html

... Or perhaps have a look at Julia:

https://julialang.org/

"Julia - to Lisp or not to Lisp":

https://m.youtube.com/watch?v=dK3zRXhrFZY

[ed: and as mentioned below, there's also wisp:

http://www.draketo.de/english/wisp

]

Make sure you use an editor, like emacs, that really understands lisp and the parentheses won’t mater. The auto indenting with lisp makes working with it syntactically just as easy as python.

I don't disagree, I did that back in university. My problem with the brackets is that it lends itself to a 'write-once-read-never' style when a function ends with 12 round brackets.

I think S-expr trees and their macros are the right way to write code, and that a S-expr diff is the one true way to do git-diff. But so far I haven't seen a language that integrates into the toolchain like that.

Go has gofmt that at least acknowledges that style should be consistent, but I would argue 'who gives a fuck'. The expression tree is what really matters.

Look into pyret. Its made by one of the racket creators. But as most commentors said use a lisp with a good editor. Emacs or atom with parinfer for example.

Yes, wisp : http://www.draketo.de/english/wisp But most lisper prefer parentheses. As for me I'm just starting to learn scheme because of GuixSD and I'm trying to get used to parentheses. It's not that bad if you use paredit/parinfer/...

Have you used wisp? I'm actually just about to work on a small github project to learn it, and was wondering if there's an editor with wisp syntax highlighting out there.

I tend to use VS Code, but it just has a plugin package named "wisp" with no documentation, looks for ".w" extensions, and is on version 0.0.1...

No, I'm just starting to learn my first lisp. I just found wisp while I was lurking on search engines for this parentheses "problem" (as I viewed it). Then I found this answer on quora and started to convince myself parentheses don't really matter: https://www.quora.com/Would-it-be-possible-to-replace-parent...

Right at this moment I'm reading this paredit guide : http://danmidwood.com/content/2014/11/21/animated-paredit.ht...

You could just write your own `read` that supports indentation instead of brackets. It would be pretty annoying, though.

Not unlike Lisp Flavored Erlang, which is a Lisp atop Erlang's BEAM virtual machine and that compiles into pure Erlang.

I thought it compiled to BEAM bytecode, is that wrong?

(From memory, don't quote me on this), The BEAM bytecode is apparently not well documented, so the standard practice for compile-to-beam languages is to emit Erlang terms, then use the erlang toolchain to compile down to bytecode. I think that's how Elixir and LFE do it anyways.

Someone correct me if I've got that wrong.

If I'm reading this[0] correctly, it looks like you're right.

[0]: https://github.com/rvirding/lfe/blob/develop/src/lfe_comp.er...