The anti-pattern becomes the new anti-anti-pattern
So, I played with lisp years ago, and other functional languages.
Somewhere along the line the notion of thinking functionally became an anti-pattern – at least from the OO camp.
So, functional thinking has returned! Apparently.
I have been watching in the background, it would always have come back IMHO.
OO tried to be the Panacea. But the biggest problem, I felt, it obfuscated the functional model for the application.
We still end up with a functional model, even if its a tacit one.
In fact, sequence diagrams, activity diagrams and even robustness diagrams of UML – not to mention BPMN, all are functional modelling approaches.
The problem is you need the right orientedness for the problem expression.
It harks back to my chattering on Jason vs Jack in the Agent Oriented world. Jack obfuscates the Agent Orientedness of the problem, making you develop with Java OO libraries.
DSL are in vogue, even if its just @nnotations in Java or Python – allowing you to create you’re own “orientedness”.
Now, don’t get me started on parallel computing – recall I used to code in OCCAM and Transputers decades ago. It is been driven by multi-core world somewhat but, of course, they haven’t architected for parallelism. Just stuck lots of cores on a substrate hoping someone would sort out the coding problem.
So, how do we do it? We don’t use OCCAM!? Although Go! is a great alternative I am thinking. Still no one gets behind mature ideas like Plan 9?! We just start afresh with same stale old ideas.