Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chapter 2 Feedback #40

Closed
reverentgeek opened this issue Jan 9, 2017 · 2 comments
Closed

Chapter 2 Feedback #40

reverentgeek opened this issue Jan 9, 2017 · 2 comments

Comments

@reverentgeek
Copy link

I just finished reading Chapter 2. It wasn't clear to me this was a chapter on JavaScript fundamentals. I kept expecting you to start mapping some of the features of functions to FP concepts, maybe in an overview fashion. As I read, I got more and more anxious with the mental tax of holding all this information "in memory" until the expected mapping began. For example, as I was reading about function arguments/parameters, I kept thinking, "Ok, I already know JavaScript, but why is this important?"

After I finished the chapter, I went back and re-read the beginning, thinking I must have overlooked something or misunderstood its purpose. All that to say, from my perspective, you should make it more clear at the start of the chapter you are covering JavaScript language features that will be important for learning FP patterns in the rest of the book.

@getify
Copy link
Owner

getify commented Jan 9, 2017

I appreciate this feedback.

The intent of this chapter is not just a general JS primer, but to drill into all of the things that are true of JS functions that must be really known to understand functional programming. In particular, my perception is that you really need to get functions from the FP perspective before you can understand FP itself, and that's the intent of this chapter. The whole rest of the book expounds on FP principles, but this chapter is our foundation: the function.

I will try to make that more explicit in the chapter intro. What I don't want to do is make it sound like you can skip this chapter if you already know JS, because I don't think I'd recommend that. :)

@reverentgeek
Copy link
Author

I agree it shouldn't be skipped. I simply made the wrong assumption, and had the wrong expectations. Making it more clear might help other readers from making the same mistake I made. The content itself was very good 👍

@getify getify closed this as completed in 2d79220 Feb 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants