Flex Without Frameworks

I have used the Swiz and Mate frameworks for Flex development, as well as an injection-framework of my own devising, and now worry about their use for applications that run on minimal-memory devices like phones and pads.  The libraries take up extra space and the benefits, such as making it "easier" to develop complex applications, not so applicable.

I like to use the presentation model in Web and Air applications but do I need that complexity for Android and IPhone apps?  And what about abstract classes and multiple-inheritance through interfaces?

A lot of apps are so "simple" in flow that having components dispatch events that are handled by their parent screens seems are lot more efficient in development terms.  Efficient in requiring less code and creating no more debugging.

To resolve these conflicts, I intend to develop an application for multiple devices and then re-factor it for the popular frameworks.
  

Digital Equipment Corp PDP-8

The PDP-8 was one of the most popular mini-computers from the mid 60's until the arrival of the first micro computers.  It was a single accumulator design and had from one to three banks of memory, each with 4K of 12-bit memory.

The memory was magnetic-core memory that didn't hold its content when switched off, and there was no ROM available at the time of the PDP-8I, so when you switched it on you had to load the bootstrap code into memory through the switches on the front panel.  This bootstrap read in a paper-tape containing a full paper-tape loader program, which could then be used to load in editors,etc.

The main storage device was a small random-access magnetic-tape unit.  This tape was block-addressable.  My first PDP-8I had the luxury of a 64k disk-drive as well.

I wrote a real-time operating system for the PDP-8i that included a 'database' -- a binary-chop system using the random-access ability of the DECTape.