I'm not really sure what this adds to programming as a practice, other than another way to represent expression trees. Building trees from data has never been t

I'm not really sure what this adds to programming as a practice, other than another way to represent expression trees. Building trees from data has never been the hardest point of building a programming language. The semantics of said expressions/statements are where the rubber meets the road. To be fair, it is much easier to program using trees, and they make metaprogramming more managable, but I suspect that the effects this has had on things like Ohayo and the like are more related to the benefits of building a DSL, and less to the ETN structure itself. Still, if you've managed to build a good visual tree editor, kudos. That is a problem that takes some consideration to get right.