3 ms·
No, I don't think that's the equivalent debate today. Structured programming vs "the old way" was about clarity of control flow. Structured programming was cl
by AnimalMuppet 5y ago
No, I don't think that's the equivalent debate today. Structured programming vs "the old way" was about clarity of control flow. Structured programming was clearly superior once you had machines with enough muscle to handle the overhead. (And once you realized that you were trying to optimize for programmer time rather than for machine time.)
I don't see expression-oriented as being similar to that at all. Expression-oriented may provide a boost to programmer efficiency, but it's not nearly on the order of structured programming vs. unstructured. It doesn't require changing peoples' mindset to realizing that programmer time is more valuable than machine time; they already know that. And, the parallel problem would be clarity of data flow, and I'm not sure that expression-oriented is a huge win in that area.
- smnplk 5y ago>> And, the parallel problem would be clarity of data flow, and I'm not sure that expression-oriented is a huge win in that area. In my opinion it is, because you can compose data transformations from smaller parts. Each part can do only one thing. For example in Clojure, you could do. (def transform (comp (do-thing-a) (do-thing-b) (do-thing-c)) (map transform my-collection) Or you could use a threading macro, with thread first or thread last semantics, which can also help you build clear pipelines. (-> basket-of-apples (select-ripe) (clean) (cut-to-pieces-of-size 4) (pack)) Not to mention transducers, which can further improve and clarify data flows.