Hmm...I still don't think that the differences between imperative, OO and functional programming are sufficient for them to be called "paradigms" and for a lang

Hmm...I still don't think that the differences between imperative, OO and functional programming are sufficient for them to be called "paradigms" and for a language that supports variations to be called "multi-paradigm" "What kinds of music do you have here" "Oh we got both kinds: Country and Western" (Blues Brothers, https://www.youtube.com/watch?v=vS-zEH8YmiM https://www.youtube.com/watch?v=vS-zEH8YmiM) Let's see: f(x) // procedural, side effects discouraged x.f() // OO, the procedures are scoped/namespaced/grouped f(x) // functional, side effects disallowed OK, that's a little facetious, but only a little. More details here: https://2020.programming-conference.org/details/salon-2020-papers/5/Can-Programmers-Escape-the-Gentle-Tyranny-of-call-return- https://2020.programming-conference.org/details/salon-2020-p... So yeah, we need to go beyond this. https://blog.metaobject.com/2019/02/why-architecture-oriented-programming.html https://blog.metaobject.com/2019/02/why-architecture-oriente...