Looking at it more, Hedy looks like it solves the latter problem reducing the barrier to entry. I wonder if something like this could be used to also keep the benefit of a common language. It looks like it allows you to choose at the beginning what language to use for authoring code, but could you use it's mapping of keywords across languages to allow a reader to choose the language they view the code in? Would that be sufficient? Maybe not because you still have variable names, function names, etc. that wouldn't have such a mapping. But I wonder how far that kind of auto-translation would get you. And how effective AI-based translation of the remainder would be, especially if paired with some sort of AST-based tooling that helps the AI to use consistent naming for the same symbols, etc. Interesting!
So they can switch the language, but its limited to the quality of natural language translation of variable names.
The RTL langs and the different numbering system, from our interview, seemed like the hardest parts she had to tackle.
Similarly, I wonder how one handles non-obvious shorthand like "rsp"
I recently interviewed Felienne for my podcast and something a lot of people may not know is that this book was born out of her struggles to teach python to 12 year olds. Out of that struggle also came Hedy. A Multi-lingual learning language that functions as training wheels for Python*.
The whole journey she went on is wild story about rethinking assumptions about programming languages and education and learning.
https://www.hedycode.com/
https://github.com/hedyorg/hedy/blob/main/grammars/keywords-...