LispCast

Making the world safe for Functional Programming

What makes some API’s become DSL’s?

Eric Normand · Published August 3, 2020

What causes an API to cross the line into becoming a DSL? Is it really a ‘I’ll know it when I see it’ situation? I’ve been searching for an answer for years. And I think I found it in a paper I read recently for this podcast: Lisp: A language for stratified design. In this episode, we go over the main factor that makes an API a DSL: the closure property.

Video Thumbnail

What makes some API’s become DSL’s?

What causes an API to cross the line into becoming a DSL? Is it really a 'I'll know it when I see it' situation? I've been searching for an answer for years. And I think I found it in a paper I read recently for this podcast: Lisp: A language for stratified design. In this episode, we go over the ma

Eric Normand

Eric Normand is an experienced functional programmer, trainer, speaker, writer, and consultant on all things FP. He started writing Lisp in 2000 and is now a Clojure expert, producing the most comprehensive suite of Clojure training material at PurelyFunctional.tv. He has a popular Clojure newsletter and blog. He also consults with companies to use functional programming to better serve business objectives. You can find him speaking internationally at programming conferences.

Related Posts

  • Can Programming Be Liberated from the von Neumann Style?
    In 1977, John Backus presented an algebraic vision of p...
    Read more
  • Do we use metacircular evaluators in real life?
    In SICP, the authors define a metacircular evaluator of...
    Read more
  • The Next 700 Programming Languages
    In this episode, I excerpt and comment on a seminal pap...
    Read more
  • The User Wizard Scenario
    We start with a Haskell type that models a feature very...
    Read more

 

Receive a weekly email to inspire functional programmers.

Subscribe for Free