Why Functional Programming Failed: Erlang, Elixir & Immutability
Full episode on youtube: • 2 Language Creators vs 2 Idiots | The Standup
Full episode on spotify: https://open.spotify.com/episode/0ilr...
Why didn’t functional programming (FP) ever take off the way JavaScript, Python, or Java did? In this episode, we talk with programming language experts Jose and Ginger Bill to break down the history, the misconceptions, and the hidden influence of functional programming on modern software development. From Erlang to Elixir, Haskell to Rust, we cover why FP ideas succeeded in some areas, failed in others, and why you’re probably using them every day without even realizing it.
Timestamps & Topics:
00:00 – Why Functional Programming Didn’t Go Mainstream – DJ asks the burning question: why isn’t functional programming everywhere?
00:58 – How FP Ideas Made It Into Mainstream Languages – Java lambdas, streams, type inference, and why FP ideas spread without taking over.
03:20 – Does “Functional Programming” Even Matter Today? – Jose and Ginger debate whether calling Elixir or Go functional is useful or just marketing.
05:34 – Functional Programming Features You Already Use – Closures, immutability, pattern matching, and other concepts that have quietly become standard.
06:43 – Why Haskell Never Went Mainstream – A look at purely functional languages, their steep learning curves, and why they remain research-focused.
08:16 – Why Erlang’s Concurrency Model Works – CSP-style processes, message passing, and immutable data in fault-tolerant systems.
11:31 – Immutability & Concurrency: The Practical Benefits – How avoiding shared mutable state makes code easier to reason about and eliminates data races.
12:42 – Could Old Java Be Considered Functional? – Exploring immutability in object-oriented languages and how it changes the FP equation.
14:48 – Coffee via SSH? – DJ’s unconventional coffee ordering method, because every coding discussion deserves a little humor.
Key Takeaways:
Functional programming isn’t dead — it’s everywhere, subtly shaping the tools and languages we -use today.
Immutability isn’t just academic; it solves real-world concurrency and reliability problems.
Languages like Erlang, Elixir, and Rust show how FP ideas can thrive in practical, modern systems.
You don’t need a “functional language” to enjoy the benefits of FP concepts — many are already in your code.
Understanding the history and philosophy of FP gives you a deeper insight into why programming languages work the way they do.
Keywords:
Functional programming, Erlang, Elixir, Haskell, Rust, immutability, concurrency, CSP, software engineering, programming languages, JavaScript, object-oriented programming, FP concepts, type inference, closures, distributed systems, fault-tolerant systems, modern programming, developer insights, coding tips, programming history
Hashtags:
#FunctionalProgramming #Erlang #Elixir #Haskell #Rust #Immutability #Concurrency #ProgrammingLanguages #SoftwareEngineering #DevTalk #CodingTips #JavaScript #ProgrammingHistory #TechTalk #DeveloperInsights
Auf dieser Seite können Sie das Online-Video Why Functional Programming Failed: Erlang, Elixir & Immutability mit der Dauer stunde minuten sekunde in guter Qualität ansehen, das der Benutzer TheStandupPodClips 20 Februar 2026 hochgeladen hat, den Link mit Freunden und Bekannten teilen, dieses Video wurde auf Youtube bereits 83,750 Mal angesehen und es wurde von 2.1 tausend den Zuschauern gefallen. Viel Spaß beim Betrachtenden Zuschauern gefallen!
