Appcelerator Titanium - Alloy vs Classic

Question

I'm about to start a new Titanium project. So far, what I've written is what's now considered as "Classic Project" (I've been writing Titanium apps since before Alloy).

I was wondering whether or not it's worth while to switch to Alloy for my new project. I know that basically, Alloy compiles to "Classic" Titanium code before compiling down to the java project or objective-c project. I also know about a big advantage in that "pre-compilation" process, which is to mark in alloy code that are relevant only for Android or iPhone and not including the other in the compiled "Classic" code.

My main concerns are flexibility - as with "Classic" I feel like I have more control over the code and what's going on.

Second concern, I have controls (like open sourced sliding menu) that are not written for alloy - how will I be able to have them as part of my project?

I started asking myself rather to use Alloy or not after finding (introduced in TiConf 2014) TI UX (https://github.com/jaraen/Ti.UX.Templates) which is written for Alloy.

few other questions:

1. how can I have old UI code run inside Alloy?
2. Can I have controls written for Alloy run in a "Classic" project?
3. Can "Classic" project also map out code not belonging to iOS/Android?
4. is there a difference in performance between Alloy projects and Classic projects? what about other flexibility issues?

Thanks

Answer 1

Just in case someone sees this question and needs an answer:

I have also posted this question in the Appcelerator Q&A where I got some answers here: http://developer.appcelerator.com/question/177739/appcelerator-titanium---alloy-vs-classic

The answer I was given is partial, and more info could be found in a questions asked here: http://developer.appcelerator.com/question/177542/classic-vs-alloy