Yes, sure, thatās an interesting point too. I like to have a clean content file too, and indeed we already lose that with blocks and layouts, and some other spots like applying hooks. I (personally) accept this āfeature lossā as itās not essential for me, I simply love the panel, and I prefer to have more content-flexibility over content-file-clarity. Having both would be sublime, of course.
This said, Kirby has always been about the simplicity of the content file. With the more recently introduced modular content structures (which are still awesome), we lose the ability to manually edit the content file : I think itās legit to expect Kirby to store content of (core?)modular fields in a cleaner way.
Maybe creating field methods serialise() & unserialise() to be optionally implemented for cleaner field storage / output ?