I'm a little biased, but I do think this is kind of amazing, especially as it shows that you can now use a language (Scheme) that occupies some of the same semantic niche as original Javascript, and have it compete in terms of speed and DOM access with the browser-specific language of the Web. Also that it lets you start constructing some of the innovations that were built up from basic Javascript, like DOM-diffing, in a simpler and potentially more rigorous way.
One thing though, even though I am getting better at Lispy languages, is that I still feel a little intimidated trying to visually parse a Lisp fragment and understand the flow-of-control compared to, say, Python. I'm not sure that I need anything more than more practice, but maybe it would also be good to have some "training wheels" to train my visual cortext to map Lisps' indentation and parentheses and iteration structures to whatever part of my brain groks control-of-flow
I think you just get used to it. Some things that can help:
1. Setup auto linting so everything auto indents and is uniform
2. Use something like paredit that helps you edit S-expressions (https://calva.io/paredit/)
One thing though, even though I am getting better at Lispy languages, is that I still feel a little intimidated trying to visually parse a Lisp fragment and understand the flow-of-control compared to, say, Python. I'm not sure that I need anything more than more practice, but maybe it would also be good to have some "training wheels" to train my visual cortext to map Lisps' indentation and parentheses and iteration structures to whatever part of my brain groks control-of-flow