I still don't really see the problem with the live button.. if your synth is ready, don't you just play with the parameters while being live?
For me it isn't really needed to be able to hear my patch "right away". I'll just build something of which I know what it will do and just go live when I'm ready.. The fact that I can write my code inside the editor is a live saver, because you can more or less instantly detect mistakes in the code.
I'm more worried about the possibility that my computer won't be able to cope with it being live all the time. I see it with synthedit already, that when I'm editing while playing, it often crashes the program (and it's not the program..).
Currently I already have a problem with the editor, where my computer completely freezes now and then when changing a parameter and needs a hard reset with the off/on button (couple of times a day for the last couple of months...). I've been told this might be caused by overloading the memory that's available to java.
So for me, the preferences would also go to dropping java for the editor, more so as I've heard several ICT friends complaining about it and asking me why the hack it's used for the editor at all.
As for further "wishes" about an axoloti 2.0..
wouldn't it be nice if the memory had an IC socket, so you could put in a bigger memory if you'ld like (even if this would ask for some DIY construction on a second board for connecting an IC of a different size). Even better if we could swap the processor..
Also, "normalised/dedicated" communication over ic2 between axoloti's is still véry welcome..