4 ms·
This does feel like a language of glyphs that can effectively communicate complexity, although, much like spark graphs, could obscure detail. But ultimately it
by th0ma5 6y ago
This does feel like a language of glyphs that can effectively communicate complexity, although, much like spark graphs, could obscure detail. But ultimately it seems like this could be powerful. Am I just acclimated to higher information density or is it really promising?
- pickledish 6y agoI'm totally with you -- I sometimes wonder what a less-pure-text representation of code could look like, what advantages and disadvantages it would have compared to lines of text, and this is one of the first full examples I've found, which is really interesting. It does seem powerful. I think the argument could be made that this is only possible with a language that uses barely any syntax, like the lambda calculus, since how would Python's 20+ keywords all translate into a graphical representation while preserving their true meaning (if statements and recursion could be straightforward, async and try/except... uh?). But it's nice to see that it's possible in simple cases, and that alone makes these harder questions seem more tractable IMO :)
- djmips 6y agoWould it not make sense to do a compiler pass on the Python first?