In this episode we chat with Adam Flater. Adam is active member of the Flex community. In addition, he is the founder of the Merapi project, which provides a bridge between Adobe AIR and Java on the client.
Resources:
Drunk on Software
A video podcast for those who like booze and bits
Drunk on Software 
Oh noes! Camera memory full!
I really wanted to hear those comments about Silverlight and having the same code base in the server and client. Bummer.
The question of Adobe’s view or “support” of Merapi came up at the Atlanta User’s Group demo of Merapi. And, the Adobe guy said basically “Hey that’s cool, but Adobe isn’t going to help.” And I think it was basically like Adam said in the video. It’s not that they don’t want it it’s they don’t want to maintain it. I’d asked at that meeting is there something Adobe can do to help Merapi? Especially with the install issue, and it was more or less shrugged off as “Well what can they do? Merapi and AIR are seperate.”
However, I could see how Adobe might give Merapi help without directly supporting it. For example, maybe the internal webkit browser could load plugins, and Merapi could be added as a plugin into AIR’s web browser.
Air would be opening itself up to extensions, but not necessarily Merapi. The merapi team could carry it the rest of the way. Are there other ways to give support to Merapi issues without making Adobe deal with supporting it or maintaining it?