Real-World Functional Programming: With Examples in F# and C# First Edition

A hallmark of this book is a very pragmatic, Rosetta stone approach to F#.Since F# lives in .Net, and .Net is inherently object-oriented; it makes sense to understand something of the mapping that takes place behind the scenes when F# code is mapped into the .Net world.Many of the interesting new features introduced into C# are actually hand-me-downs from FP (functional programming). This includes generics, LINQ, anonymous methods, lambdas, type inference, etc.. Since many programmers need to use C# in the work-a-day world, it makes sense to understand the functional elements of C# by seeing them in a functional language like F#, where they can be seen in their purest (least hobbled) state. Once these concepts are understood, it is then much easier to understand how to wield these tools effectively in C#.That said, there are also limits to how much functional programming can be done in C# (and how effectively it can be accomplished). This book clearly demarcates the boundaries of what is (and isn't) feasible in C# vis-à-vis functional programming.One of the things I liked best about this book is the discussion on why functional programming makes code easier to read, write, and verify. This discussion does not appeal to what might be (for many) inaccessible theory (i.e. denotational semantics, category theory, etc.). Instead it is demonstrated in amazingly simple, straightforward ways! This discussion is very effective.Another facet of this book's approach that I applaud is the demonstration of lambda calculus. Why would a practical book dabble in theory? There's actually a very pragmatic payoff in doing this: functional programming has a lot of underpinnings in lambda calculus. Those that have been exposed to lambda calculus will feel right at home in F#. Those that haven't are likely to feel more "culture shock" when being exposed to concepts like currying and lazy evaluation. Functional programming really does represent a substantially different way of thinking about computation.This book also features an excellent discussion about design patterns; comparing and contrasting how they are implemented in OOP (object-oriented programming) versus FP. Some classic design patterns in OOP essentially come for free in FP (e.g. the "visitor" pattern).

I purchased this book about a year ago, but didn't begin reading it in earnest until recently. (I'm generally been interested in functional programming, but not until recently have I decided that a scientific application I've been writing would probably benefit from domain logic written in a functional language.) I'm about 60 pages into the book, and loving every second! This book is geared toward teaching *fundamental functional principles* from an OOP starting point. The presentation of F# syntax, while present, seems secondary to the fundamentals.What has really struck a nerve in me is how much greater appreciation I have for the weaknesses that C#/OOP can present. For example, the author's discussion of side effects and mutability (OOP programmers accept this an move on), were placed in a new (and insidious) perspective for me. Have any of you studied the many functional influences grafted into the C# language (e.g., generic delegates, LINQ) and thought, "There's some larger perspective here I'm not being told?" (Almost like a joke you're not being let in on?) This book gives you that larger perspective. I have already had many moments of revelation.Will this book compel me to abandon C#? Will it convince me to take up F#? I really don't know, and I don't care. Fundamentally, this book is giving me a fresh perspective into C#, and the book is well worth the price of admission right there. To the extent that I'm also learning functional programming concepts, all the better!I also offer my thanks to Manning, who has put together a mind-blowing collection of C# titles. Thanks so much![Full disclosure: I'm a non-professional, enthusiast programmer (C#/WPF), so qualify my opinion with that perspective.]

Good book with decent coverage of functional programming in F# and the functional capabilities added to C#.

I usually don't like tutorial-style books, but am finding this one invaluable. More than the other F# titles to date, it explores at length what makes functional programming different, and what this means in a .NET context. A unique feature is the running comparison of F# with both traditional and "functional style" C#. Code listings are nicely labeled with arrows pointing out important details. The book is not intended as a language reference, and only lightly touches on the imperative and object-oriented sides of F#, or contents of standard .NET libraries, but this allows a more leisurely and thorough treatment of the distinctively functional concepts and their implications for program design. Highly recommended.

I have mixed feelings about this book; which I purchased along with Functional Programming using F#. Although Real-World Functional Programming is similar to other Manning publications in being more pragmatic and useful for practitioners, I skimmed over the C# examples since I was interested more in seeing how F# implements functional programming concepts. For a basic introduction, start with the F# Software Foundation Documentation. For a more in-depth understanding, I believe Real-World Functional Programming by Manning is a good second book to read. And finally to begin practicing, I like Functional Programming in F# which includes a lot of exercises and is written more like a college textbook. Real-World Functional Programming does hold-your-hand a lot and depending on your programming experience that can be either good or bad. I would prefer a shorter book that could be used more for reference with examples in F# only. But I bought the book because it was written by Tomas and I believe he did an excellent job of covering F#.