This book explores the core principles of functional programming (FP) that can be applied to JavaScript. But what makes this book different is that we approach these principles without all the heavy terminology. We look at the subset of FP that I call "Functional-Light Programming" (FLP) and apply it to JS.
Let's face it: unless you're already a member of the FP cool kids club (I'm not!), a statement like, "a monad is just a monoid in the category of endofunctors", just doesn't mean anything useful to us.
That's not to say the terms are meaningless or that FPrs are bad for using them. Once you graduate from Functional-Light, you'll probably want to study FP more formally, and you'll swim in the depths of those terms.
But I want you to be able to apply some of the fundamentals of FP to your JavaScript now, because I believe it will help you write better, more reasonable code.
To read more about the motivations and perspective behind this book, check out the Preface.
- Foreword (TBA)
- Preface
- Chapter 1: Functional Functions
- Chapter 2: Managing Function Inputs
- Chapter 3: Composing Functions
- Chapter 4: TODO
It is expected this book will eventually be published, but nothing is in the works yet. Keep an eye out for future updates here!
If you'd like to contribute financially towards the effort (or any of my other OSS work) aside from purchasing the books, I do have a patreon that I would always appreciate your generosity towards.
The content for this book derives heavily from a training workshop I teach professionally (in both public and private-corporate workshop format) of the same name.
If you like this content and would like to contact me regarding conducting training on this, or other various JS/HTML5/Node.js topics, please reach out to me through any of these channels listed here:
I also have several JS training courses available in on-demand video format. I teach courses through Frontend Masters, like my Functional-Lite JS workshop. Some of those courses are also available on PluralSight.
Any contributions you make to this effort are of course greatly appreciated.
Please feel free to contribute to the quality of this content by submitting PR's for improvements to code snippets, explanations, etc. If there's any doubt or if you think that a word/phrase is used confusingly, before submitting a PR, open an issue to ask about it.
However, if you choose to contribute content (not just typo corrections) to this repo, you agree that you're giving me a non-exclusive license to use that content for the book, as I (and any future publisher) deem appropriate. You probably guessed that already, but I just have to make sure the lawyers are happy by explicitly stating it.
This book will go through official editing eventually, and typos will likely all be caught at that stage. As such, typos are not a big concern of mine for now. If you're going to PR for typo fixes, please be measured in doing so by collecting several small changes into a single PR (in separate commits).
Also, if you have any questions or concerns, please make sure to search the issues (both open and closed!) first, to keep the churn of issues to a minimum. I want to keep my focus on writing the book as much as possible.
The materials herein are all (c) 2016 Kyle Simpson.
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 4.0 Unported License.
