I think the divide between imperative and functional programming is largely an arbitrary one. If you write a for-loop where each iteration doesn't refer to ano

I think the divide between imperative and functional programming is largely an arbitrary one. If you write a for-loop where each iteration doesn't refer to another iteration, then the compiler should be able to swap between either notation on the fly. So I'm frustrated that we haven't adopted a kind of "bridge" programming with immutable data, and dealing with the transformations that are being done. Basically everything would be a black box, like a series of small simple programs running in the same heap. Like a unix VM running inside the program, and just pipe data around. Yes, functional programming makes easy things hard, and imperative programming makes strong things weak, but anymore I think of it as limitations in compiler and mindset more than anything else.