3 ms·
Oh god. They basically just took Go and added unnecessary parenthesis. This is the worst way to make Go LISP-like.
by c3534l 11y ago
Oh god. They basically just took Go and added unnecessary parenthesis. This is the worst way to make Go LISP-like.
- jdc 11y agoWhat's the best way to make Go more LISP-like?
- c3534l 11y agoKeep the functional semantics and functions, but with the basic Go syntax. If, as others have said, they don't see the parenthesis after using LISP for a while, then why bother adding them into Go in the first place?
- iagooar 11y agoIn my opinion, people who complain about Lisp's parentheses are usually the ones that have absolutely no idea about Lisp, nor have they any experience with it. Once you get "into" Lisp, you do not see it as a bunch of parentheses anymore, so focusing on this aspect suggests that the person who does it, does not really have much previous experience with Lisp.
- pjmlp 11y agoYeah. func(a,b) => (func a b) if ( a > b) { => (if (> a b) something) // something }
- chriswarbo 11y agoPlus the fact that a decent editor will handle the parentheses for you. When programming in Lisp, I use Emacs with paredit (for inserting and manipulating parentheses, quotation marks, etc.) and have the default colour for parentheses be very similar to my background colour, so I can focus on the symbols and their indentation instead. The exception is when the cursor is next to an open/close parenthesis, in which case the matching parenthesis is highlighted.