> there are a host of specialized optimization strategies only possible when compilation can happen during runtime That's a big part of why Jank is interesting

> there are a host of specialized optimization strategies only possible when compilation can happen during runtime That's a big part of why Jank is interesting to me, because it can properly embrace the idea of runtime JIT using LLVM. The JVM may still have an edge with profile-guided optimization for the foreseeable future, but perhaps Jank can help close that gap and support even more advanced possibilities for data-intensive workloads, e.g. along the lines of https://www.lingo-db.com/ https://www.lingo-db.com/