3 ms·
He began by building the engine, and to do this he used the ‘HotSwap’ functionality of the Java JVM 1.4.2, which continuously updates the running code
by technomancy 15y ago
He began by building the engine, and to do this he used
the ‘HotSwap’ functionality of the Java JVM 1.4.2, which
continuously updates the running code when it detects
that a class has changed.
If anybody at Google is reading this, if you add this
feature to the Android emulator and I will literally
drive to your house and kiss you on the mouth.
Indeed, the fact that Android doesn't already have this makes it hard for me to take it seriously as a platform. Immediate feedback is crucial to any development environment.
- aboodman 15y agoUse an actual device, not the emulator. The emulator is super slow, but with an actual device you can have 30s iteration times. Edit: I know 30s is still nowhere near ideal. Hell, on Linux Chromium (a massive project) we have faster iterations than that. But it's good compared to the Android emulator. I think you should be able to go even faster, but I need to dig into how Ant actually works. It seems to be redoing more work than necessary for each build.