3 ms·
Other comments make it sound like dropping parentheses is just a craven attempt to make Racket more popular. To me, this epitomizes the distinction that the mai
by laughinghan 7y ago
Other comments make it sound like dropping parentheses is just a craven attempt to make Racket more popular. To me, this epitomizes the distinction that the maintainer drew between trying to get more popular, and lowering barriers of entry. If Racket 2 is no more popular (it loses as many community members as it gains), but the new community members had an easier time joining the community yet still love Racket 2 just as much as the old community loved Racket 1, isn't that still a win?
Conversely, if it turns out that everyone loved Racket 1 not because of the design elements that the maintainer put so much blood, sweat, and tears into, but because of the high barrier of entry due to the parentheses (the one thing that the maintainer didn't put effort into), how is that at all motivating to the maintainer?
I'm less of a community member and more of an admirer of Racket from a distance (and I don't mind parentheses, really, I've used Clojure professionally and it was great), but I look forward to seeing how this initiative turns out.
- anaphor 7y agoFrom some of the comments it feels like this is also intended as a way to research different ways of doing Lisp surface syntax without sacrificing the features of the macro system. I'm not sure if it's possible to do both at the same time.
- laughinghan 7y agoDid you miss the "How?" section of the post? He wrote a research paper showing it was possible in 2012, "Honu: Syntactic Extension for Algebraic Notation through Enforestation".
- anaphor 7y agoYes I read the paper, but he also makes it clear that there's still lots of work to do (e.g. how to make it work better with macros)