> In fact, I believe a good method-based JIT is probably more complex than a trace-based one. When compiling at method-granularity, with incomplete information

> In fact, I believe a good method-based JIT is probably more complex than a trace-based one. When compiling at method-granularity, with incomplete information about types, complex features are required e.g. On-Stack Replacement (if the current method becomes "hot", it needs to be replaced by a compiled version), Inline Caches, Hidden Classes and Deoptimization. Don't you have exactly the same problems in a tracing jit? For example, if the running while-loop becomes hot it would need to be replaced with an optimized version of it.