Johannes Neubauer

regarding 1.: I do not prefer BFS over DFS here, but the orignal blog post did not have a cycle detection. This is why I wrote "e.g. a BFS".

regarding 2.: For very deep structures you are right.

I use the collection only in a single operation (I mention this in the post) so there is no need for additional locking (the set is used only internally). Beside being a one-liner, which is nice for a block post, I had no further reasons to use the synchronized-wrapper. Is there a real issue using it in this case here, or is it more a "don't use this in general"-thing?

You may use `Seq` of Jool, combined with `Iterables.concat()` of guava, but then you cannot parallelize it anymore... It's a tradeoff...

The language is well-suited for usage on Android, too. But for the target group "DSL creators" the most compelling feature is, that Xtend is itself a "DSL" (a general-purpose one) created with Xtext. The cool thing about this -- beside mind boggling coolness -- is that you can reuse parts of Xtend (e.g. Xtend expressions) in your own DSL, which makes it familiar and reduces the effort to create a DSL. Beside that, it has an even better compatibility to Java than Kotlin. Last but not least, it compiles to Java and not to bytecode, which has some advantages and some disadvantages.

We use Xtend (you spelled it wrong) at TU Dortmund a lot. It is "part" of the Xtext project for creating DSLs. Xtend has some nice properties other languages have not and some intricacies other languages have not (but you can say that about every language). Everything is an Expression, Extension Methods, Multiple Dispatch, Type Inference, and Active Annotations (Meta-Programming) are some of them.

Thanks. Sure! I'm working on a web app build with DIME that describes itself as a landing page. Bootstrapping rules. I keep you updated.