Fishbowl @ Functional Conf
summary
A freeform panel explains concrete tradeoffs: companies move from Ruby to Elixir for backend to gain reliability while keeping Rails for UI; a data team runs hundreds of Scala jobs with Scala + Akka on ~100 AWS nodes crawling ~1B pages/month; one C++ product gets rewritten in OCaml by five engineers and ships successfully to Citrix; XML-to-JSON conversion is solved with small partial functions instead of sprawling class hierarchies; languages, tooling and monitoring shape real concurrency choices.
AI-written summary · about
chapters (19)
- 0:00Fishbowl format intro
- 2:15Panelists and rules
- 3:01First audience question
- 10:49Learning multiple languages
- 11:18Concurrency models in FP
- 17:19Choosing functional languages
- 20:28Moving to functional languages
- 23:14Benefits of functional programming
- 29:34Dynamic XML with FP
- 33:04Language vs execution evolution
- 37:38Language design psychology
- 41:52Dynamic to static typing
- 42:38After functional programming
- 46:36State pollution and paradigms
- 49:00FP patterns in UI/system
- 51:47Reactive programming in UIs
- 53:54Immutability and testing
- 59:50Migrating teams to FP
- 1:00:53Closing remarks
related talks
46mThoughtful Software Engineering
31mPanel Discussion
01h 01mArchitecture Decisions: A Case Study -
45mKeynote: One Monolith, Many Teams: Growing an Org...
01h 15mFunctional Mechanical Sympathy
37mModern Abstractions and the Web, and avoiding Pitfalls because Life is short
33mFrom Enterprise Architecture to Software Design - Critical Thinking
01h 02mTools for simplified large scale systems