The whole Pale Moon project doesn't even make sense to me. They could have just broken the browser toolkit out of comm-central (SeaMonkey) and built on top of t

The whole Pale Moon project doesn't even make sense to me. They could have just broken the browser toolkit out of comm-central (SeaMonkey) and built on top of that if the 'Classic' interface is what they are looking for. This solves the problem of the classic interface, current security patches, and modern Firefox HTML5 support. There is no way that their tiny team can resurrect all of the old APIs that Mozilla has been decimating recently (XUL/XPCOM extensions/add-on SDK, complete themes, non multi process extensions, unsigned extensions, etc.) With all of the talk about breaking Thunderbird (and, ostensibly, SeaMonkey) out of the core Mozilla infrastructure, the future does not look bright. I am honestly unsure as to what I'll do when SeaMonkey finally dies. I use an xpfe complete theme, maintain a SM/Thunderbird add-on that directly modifies the browser XUL to display picons/X-Faces/Faces/X-Image-URLs/etc, maintain an add-on that loads the old add-on manager in a separate (non-incontent) XUL window, etc.