Scott Wlaschin - Railway oriented programming

[@piezocuttlefish]

I've been watching Scott's presentations for years. I think this is the most complete and most well-structured of his talks yet.

[@wuzixiao1]

Thanks for your great video. TIL: dont use this exception for control flow and you shouldn’t catch programmer error or system error, only error for domain models.

[@sirstroam]

I love the pacing in this video.

[@alexoleynikov717]

Thank you, Scott, for this amazingly clear presentation! Just like your book "Domain Modeling Made Functional", which is also a great read.

[@iurysza]

This is an amazing talk! I've seen and even implemented some of these concepts before, but I never saw them put so nicely together like this. Thanks!

[@thomassteindl9481]

Yes, I think this is so far the best and most easy to follow. Would love to see that for Scala.

[@JohnMcclaned]

19:41 - Scott really swallowed that oyster like nobody would notice

[@SystemAlchemist]

The Roman Numerals code is very simple and elegant. It is also very inefficient. I suggest the example in the book Thinking Forth p.122 for two different versions of doing it differently.

[@xerxesking6734]

Thank you

[@digitalspecter]

It's a shame that Rails isn't inspired by this..

[@shalokshalom]

Saturn is shaped like Rails with this in mind So very opinionated MVC with composition and functional programming Much fun 😊

[@magne6049]

Elixir on Phoenix allows this style, and is a FP oriented Ruby on Rails like experience. Elixir was made to resemble Ruby.

[@MateusCruz]

You can achieve the same type of pattern with the dry-monads and dry-transaction gems. Been using them for a while.

[@magne6049]

or even Gleam language which is also based on Beam and interoperable with Elixir and Erlang and even compiles to JS!