I'm trying to work out just why that concerns you that much (aside from pride in one's creation)

Emplode handles the supported functionality of the empeg well, and although there are a few quirks, I can't see any major improvements that are needed...

But JEmpeg (I believe it got renamed) handles some of the third party stuff developed here - eg hijack updating, boot logos/animation updates etc, that I can't see you supporting officially in Emplode. And the portability is a big issue for a small percentage of us...

One feature that JEmpeg has that I really like is the faux on-empeg-soup playlists. But it is a bit of a kludge - the playlist soup definition is not stored on the empeg at all, but in JEmpegs rc file. As far as Emplode woud be concerned the playlist would be static. And ditto if you used JEmpeg on another machine. But in terms of usability it does work very well.