Arrow functions should be used only for callbacks. I hate that people has started defining named functions with arrow functions in JS. Arrow functions are not hoisted and the ordering of your functions is going to get wonky, because you need to define all you functions first before composing them, when it should be the other way around. Start with the most high-level function which calls lower level functions.
I’ve reached the point that I cringe at the mention of arrow functions because so many people seem to always want to use arrow functions.
Like I’m looking up something on stack overflow and half the answers are arrow functions that are that way for no other reason than to use the fun little =>
Who doesn’t use arrow functions?
Arrow functions should be used only for callbacks. I hate that people has started defining named functions with arrow functions in JS. Arrow functions are not hoisted and the ordering of your functions is going to get wonky, because you need to define all you functions first before composing them, when it should be the other way around. Start with the most high-level function which calls lower level functions.
I had this exact fight with my team several months ago, and lost to popular opinion since the rest of my team are either zoomers or indifferent.
I’ve reached the point that I cringe at the mention of arrow functions because so many people seem to always want to use arrow functions.
Like I’m looking up something on stack overflow and half the answers are arrow functions that are that way for no other reason than to use the fun little =>
I think there’s also a good case to use them if your function is just evaluating and returning a single expression.
sum(your_mom <- rep(69, 420))R?
NaN
your_mom is undefined
It’s being assigned and passed to
sumat the same time. One of the many entertaining quirks of R.