> To the extent that I have a programming style, I find myself increasingly thinking of it as Primitive-Oriented Programming. If you want your final program to

> To the extent that I have a programming style, I find myself increasingly thinking of it as Primitive-Oriented Programming. If you want your final program to have some desirable property, be it correctness, scaling, parallelizability, or even more complicated things like one I work on where the interface must have the property "able to be remoted across this certain protocol for various reasons", the best way to achieve that in general is to create primitives with this property, create ways to combine them that maintain the property, and build up from there. Do you have any experience with the APLs? They also strive for this sort of functionality - they're based around a set of primitives which have implicit looping and high potential for parallelism. I have been experimenting a lot with k (kona) lately; it and J (http://jsoftware.com http://jsoftware.com) are both definitely worth a look.