Hi Zelphir, Your concerns are absolutely warranted.
>From what I've seen there is no advantage that editors can give you with parens, that they can't do better without parens, *given that you've written loads of tests and done the grunt work to make that happen*. Hence, it doesn't make sense to advocate for removing parens for Racket2 until all the code and tests are written for the different editors that make the parens-less experience fantastic, and folks can compare the 2 side by side. So if folks are working toward that, please let me know as I'd love to help out. -Breck On Mon, Jul 22, 2019 at 12:17 PM Zelphir Kaltstahl < [email protected]> wrote: > I just want to give one thought as input to this discussion and will > admit, that I did not read every (but some) of the posts above. > > When I write code in Racket or Scheme, I mostly like the parentheses, as > they make writing the code easy. I can very easily select a block and move > it around, without introducing any syntax errors. I can also quickly see > what the scope of something is, what other expression it is in. I don't get > these things from languages without this many parentheses or without > s-expression syntax. I need my parentheses as markers for my cursor to > quickly jump around. It is the most pleasant code typing experience I've > ever had. So when considering to move away from parentheses, please also > consider the burden that those parentheses take away from the person > writing the code. When I edit for example Python code, things are not clear > when moving around code. This is worse in Python than in other languages, > which at least have curly braces (but usually some other annoying > deficiencies). If there was a move away from this many parentheses (read > markers for my cursor), it would have to provide equal editability, for it > to be attractive to me. A design based on indentation or something like > that is not going to cut it for me. And what else would be used as start > and end markers for expressions? Wouldn't that in essence just be another > form of "parentheses", just looking different? How would any editor know, > where an expression starts and ends for easy selection and moving around, > if there were no such markers? So far I got no idea how that could be done > without introducing loads of new constraints about how you can nest > expressions into the language. So it beats me. Maybe my imagination in this > area is still somewhat limited. > > Just my 2c. > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/racket-users/bf0b5dd1-8802-4c78-af7a-4231ae30ad60%40googlegroups.com > <https://groups.google.com/d/msgid/racket-users/bf0b5dd1-8802-4c78-af7a-4231ae30ad60%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CAOgHByu0RLROGMvdXxO0uCTDGN69u%3DgAp8c%2B9vtiSzSPRF91Dg%40mail.gmail.com.
