Not exactly sure of the technical reason, or even whether it is down to the software or hardware aspect of Axoloti, but there are two very obvious and frustrating limitations with the current Axo system:
1 - I think the design of the hardware suggests that sampling and recording-focused projects were not given as much credibility as, say, analogue modeling synths etc, during it's design. What might surprise you though, is that it is always sample-based sketches, objects etc that generate the most interest from users of this forum. Whether it's just an object for looping or something more elaborate it is always the sample-based stuff that generates the most interest.
This does not surprise me in the least, because it shows that the sample-based oblects are far too low-level for most users, and that much more thought needs to be put into their design and abilities. For example, a layman coming to Axoloti is going to expect a sample-based object to contain connections that access start point, end point, current position read/write, loop mode, and reverse, and for all the 'tech stuff' to be dealt with by the object itself as opposed to masses of external objects and complexity eating-up RAM and complicating things.
2 - Same goes for recording and playing back audio as a multi-track recorder would. I would love, for example, to create a very basic no-thrills digital multi-track recorder, but with the current Axo, no chance, not unless I was some low-level code guru. The current Axo lacks the RAM to build a comfortable system, and it lacks optimised full-duplex recording/playback objects.
These are both very obvious shortcomings for a digital audio system designed to allow the consumeer to build what they need. It is especially frustrating because the hardware has both audio ins and audio outs.
Like I said, I suspect that sample and recording based stuff was not what Johannes had in mind, I think he was thinking more along the lines of analogue modeling and other more experimental stuff.
So in a nutshell, what I'm saying is that those two areas absolutely need to improve, and as Johannes is currently pre-occupied with the live system he's working on, maybe you will give the matter some thought for the version you are working on.