Joy (implemented in Prolog) could tick some of these boxes. > window2 is an optimized version of window1 and should have the same outputs for every input. I sh

Joy (implemented in Prolog) could tick some of these boxes. > window2 is an optimized version of window1 and should have the same outputs for every input. I should be able to encode that in the language, and have the tooling generate checks showing the two are the same, and also run benchmarks testing if the optimized version actually is faster. That should be possible with Joy, it's certainly something I want to explore. The interesting semantic relationships are those that let the machine automatically deduce optimizations > I also like the idea of modifying function definitions at runtime. I have these visions/nightmares of programs that take other programs as input and then let me run experiments on how the program behaves under certain changes to the source code. I want to write metaprograms dammit Lotta metaprogramming in Joy. Many functions work by building new functions and running them, it's a natural idiom in Joy. - - - - > A language designed around having first-class GUI support Red? ( https://www.red-lang.org/ https://www.red-lang.org/ ) > Visual Interface Dialect ... is a dialect of Red, providing the simplest possible way to specify graphic components with their properties, layouts and even event handlers. VID code is compiled at runtime to a tree of faces suitable for displaying. https://github.com/red/docs/blob/master/en/gui.adoc https://github.com/red/docs/blob/master/en/gui.adoc > You can’t work with strings, json, sets, or hash maps very well, date manipulation is terrible, you can barely do combinatorics problems, etc etc etc. I want a language that’s terse for everything. That also sounds like Red.