Life After Business Objects
summary
A team describes moving from mutable business objects to functional approaches: they explain why they adopted F#, how they changed domain modeling, and what replaces traditional business objects. Another presenter explains why their project stayed on C# while combining OOP and functional paradigms in C#, and which kinds of problems still justify switching to F#.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:11Point class problems
- 9:03Method visibility
- 13:20Data and logic separation
- 16:58Joe Armstrong on business objects
- 21:36F# and C# Next modeling
- 27:11Currying and dependencies
- 32:10C# functional evolution
- 37:50When to switch languages
- 44:10Computation Expressions in C#
- 47:28Conclusion
related talks
34mLife After Business Objects - Confessions of an OOP Veteran
35mLife After Business Objects - Confessions of an OOP Veteran
37mLife After Business Objects: Confessions of an OOP Veteran
44mLife after business objects. Confessions of an OOP veteran
46mFunctional developer in object oriented world
37mLet's get more functional
01h 05mFrom object oriented to functional domain modeling
58mFunctional Toys in an Object-Oriented Sandbox
