Why are FP devs obsessed with Referential Transparency?

An explanation of referential transparency, its relationship to side effects, and common misconceptions in functional programming.

Hate watching videos? Check out the complementary article, which covers the same content: dev.to/zelenya/why-are-fp-devs-obsessed-with-referential-tra… We clarify referential transparency, why it is so cool, what it has to do with side-effects, and what common misconceptions are. For instance, how can the code have no “side-effects”, but the program can print to the console? 💡 If you want some recaps or cheat sheets, check out these pictures: * What is Referential Transparency: impurepics.com/posts/2018-04-01-referential-transparency.htm… * Referential Transparency in the Wild: impurepics.com/posts/2018-07-13-referential-transparency-wil… #fp #haskell #rust #scala Subscribe to Impure Pics: bit.ly/impure-youtube *More Impure Pics* 🐣 twitter.com/impurepics 📦 impurepics.com 👕 merch.impurepics.com *Functional Alphabet book* 📗 Softcover: bit.ly/fp-abc-soft-cover 📘 Hardcover: bit.ly/fp-abc-hard-cover *Watch more Impure Pics* youtube.com/watch?v=c7FncTzvpUQ&list=UULF9-egQYdpElHtvVM-t9q… *About Impure Pics* FP Advocat. Distilling functional programming for the good of all Get in touch: zelenya.com 0:00 What is Referential Transparency? 2:25 Why should I care? 4:13 What are side-effects? 5:01 RT in Rust 5:55 RT in Scala 7:52 RT in Haskell 9:19 RT trivia 10:11 Conclusion