Elixir enables stateful web applications, is it wrong to think like this?

I came across the idea via Why getter and setter methods are evil (2003) - more recently Allen Holub has been going with the “Tell, Don’t Ask” moniker in his OO talks. And most sources seem to ultimately point back to pragprog.

Steve Vinosky’s stance on RPC.

I keep quoting Convenience over Correctness (2008) hoping somebody will listen.

interpret it might be at odds with Alan Kay’s “The important thing about objects is message-passing”.

Alan Kay’s insight is enlightening as it moves focus away from “the mighty object” but it could still be considered myopic.

I’m referring to Protocols as discussed in Thinking like an Erlanger.

The software industry got caught up with CASE tools while Class-Responsibility-Collaboration (CRC) Cards (1989) got largely ignored. Lots of attention to Classes (Objects) and Responsibilities but the dynamics of Collaboration - not so much. People focusing on individual trees and ignoring the forest.

PS: Some further discussion on To spawn, or not to spawn?

1 Like