Skip to content
0:00 / 0:00

#interpreterpattern#scala#functionalprogramming

The Interpreter Pattern Revisited

InfoQ

234K subscribers • 65 videos on Hallway • Conference channel

YouTube
  • Recommended by 2 people: 1 on Lobsters and 1 in engineering communities.
  • A classic. People kept recommending it from 2019 to 2025.
  • Presented by Rúnar Bjarnason
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

19K views11 years ago2 recommendations

Software designProgramming languagesDesign patternsFunctional programmingScala

Rúnar Bjarnason revisits the classic Gang of Four Interpreter Pattern, arguing that it is the most useful design pattern for functional programming.

Rúnar Bjarnason calls the Interpreter Pattern "a classic object-oriented design pattern that has been overlooked by far too many for far too long. In this talk we will give this unsung hero the accolades it deserves." He brings us back to 1994, when the so-called "Gang of Four" published a book called Design Patterns: Elements of Reusable Object-Oriented Software, revisiting the often buried chapter on the Interpreter Pattern, and arguing that it is the most useful pattern in the entire book. Watch the 13 talks from NE Scala 2015: crcl.to/bdvun Scala Training from NewCircle: crcl.to/chrua nescala.org/

Why it's here

2 people recommend this

What people say. Recommended as a classic talk on how the interpreter pattern bridges object-oriented design and functional programming.

u/_jackdk_in r/haskell • Recommends

On “What is the 'Design Patterns' equivalent book in functional programming world?”

Many of the "classical" design patterns from the GoF don't really apply cleanly to Haskell because so many of them do things like reimplement partial application by storing some arguments in an object, or implement objects with a single "invoke" method to imitate functions as first-class values. Built-in language features render such patterns unnecessary. (Exception: the Interpreter Pattern, which Steve Yegge calls "the only GoF pattern that can help code get smaller", and the subject of a great Scala talk by Rúnar Bjarnason). The "just use functions" advice is simple and true, but probably not helpful until you've already internalised it. Many of your software engineering instincts still…

endgameon Lobsters • Recommends

The Interpreter Pattern Revisited (2015)

u/MasGuiScalaKata.comin r/scala • Mentions

On “Modelling standards and good practice in Scala ?”

Watch this video!