It seems to me (from the last meeting notes) that the map range node is kinda duplicated into the easing node and the mix node. Mix does different data types but only linear interpolation, easing does just float type but all kind of interpolation, and map range seems redundant now. It would be nice to keep things as tidy as possible and follow the recent mantra “don’t group by type, group by functionality”. I’d vote for a single node handling all types and interpolation options (not that I use them a lot, linear would be enough for me). Unless of course I am missing something there ?
Also did you consider extending the math node instead of making a separate integer math node ?
I am asking because of this statement :
Generally we want to move to an operation based workflow rather than a data type based workflow.
that I tend to agree with