ah folks? ahh... if you actually want xulrunner as a pyjamas desktop runtime, now would be a good time to help defuse an argument in which i'm rapidly getting out of my depth because of the mozilla foundation's focus on "speed, speed, speed" and "javascript, javascript, javascript".
so far, i've learned that ben smedsburg, who is responsible for embedded mozilla, made decisions to terminate support for a number of mozilla-sponsored embedded technologies in order to save resources. the decisions made were ones that i actually agree with, for example gtkmozembed, which was incomplete and so gained absolutely no traction. unfortunately, ben isn't _actually_ familiar with how dynamic programming languages like python actually work. as a result of that, the python-xpcom code, which is a critical dependency, simply isn't getting any development (at all). the core developers have never even run hulahop (which is what gtkmozembed _should_ have been). ever. the OLPC team have got so sick of this, and are so angry at the mozilla foundation that they've terminated all use of hulahop AND removed ALL mozilla applications (firefox etc.) from their computers. so. if you actually ever want xulrunner as a pyjamas desktop runtime, now's the time to help arbitrate, explain and stand in the way to make sure i don't get even more angry with them than i already am. the irony is that if they actually ran hulahop it would provide an additional testing framework which could be used to help pinpoint bugs from alternative angles. apart from being extremely cool in its own right. but right now because of their intransigence and lack of knowledge of the workings of their own code, _and_ because i'm socially inept _and_ because i'm not familiar with their communications infrastructure nor with the codebase, we're losing traction. help, folks. the topic is "the future of binary embedding", and it's on the mozilla public forums. l.
