In your example you are displaying a typical subroutine thus this does make sense but if you are making everything a subroutine than you are not conveying the boundaries of you application very well are you?
Cofounded Host Collective (DiscountASP.net). Cofounded Player Axis (Social Gaming). Computer Scientist and Technology Evangelist with 20+ years of experience with JavaScript!
People often use the readability argument to argue against arrow functions. Not able to see what is and is not a function. That is just a matter of organization.
Put constants in one place, put functions in another. You should do this with or without arrow functions.
Cofounded Host Collective (DiscountASP.net). Cofounded Player Axis (Social Gaming). Computer Scientist and Technology Evangelist with 20+ years of experience with JavaScript!
In your example you are displaying a typical subroutine thus this does make sense but if you are making everything a subroutine than you are not conveying the boundaries of you application very well are you?
People often use the readability argument to argue against arrow functions. Not able to see what is and is not a function. That is just a matter of organization.
Put constants in one place, put functions in another. You should do this with or without arrow functions.
I have no problems seeing what is and what is not a function.
In the case of currying... I find the
function
keyword to be much harder to read.I'm not fully understanding this