Some of these points are true of currying in general -- IMO most of the time you can't tell what's a function call and what's a curry (Haskell people would say

Some of these points are true of currying in general -- IMO most of the time you can't tell what's a function call and what's a curry (Haskell people would say "its the same thing!"). However, separating these concepts leads to a lot of super interesting results. I wrote about this in this blog post: http://tolmasky.com/2016/03/24/generalizing-jsx/ http://tolmasky.com/2016/03/24/generalizing-jsx/ . I argue that the JSX syntax makes for an awesome syntax for currying. Edit: Some follow up articles: 1. Using this scheme, you can actually have default parameters in currying: https://runkit.com/tolmasky/default-parameters-with-generic-jsx https://runkit.com/tolmasky/default-parameters-with-generic-... 2. An example of how to apply this to Babel syntax trees: http://runkit.com/tolmasky/generic-jsx-for-babel-javascript-ast http://runkit.com/tolmasky/generic-jsx-for-babel-javascript-...