Yes, it's still the case that language implementors have to work around the JVM's lack of support for tail call optimization. It's not a big deal for most apps

Yes, it's still the case that language implementors have to work around the JVM's lack of support for tail call optimization. It's not a big deal for most apps. I leave TCO turned off with Kawa Scheme not because it's a performance problem, but just because it's the default and I don't usually need it. The only code I have compiled with TCO enabled was for maze generation, and I don't think it slowed it down much: http://brlewis.com/amaze.brl http://brlewis.com/amaze.brl