Closed koresar closed 7 years ago
Does it really need to be a breaking change? I mean you can add the alias now and keep good old compose
there, maybe even with some deprecation warning if you like. I wouldn't certainly advice to just go over the hoop and change it.
Personally, I don't mind compose
and I don't like much blend
, but whatever :)
Yeah. Alias looks like a better idea.
I think this is a bad idea.
compose()
actually does do object composition to produce the descriptorscompose()
actually does set up function composition (which is exactly what happens when init functions are applied)compose()
.In short, if it ain't broke, don't fix it.
The entire point of stamps is stamp composition, which you're right to describe as distinct from both function and object composition, because it fuses the two -- but calling it something other than composition would be a colossal identity blunder, and would cause a lot more confusion.
All valid points. Closing.
Proposal: use more accurate and a less confusing word for the
compose()
function.The core of this specification is the
compose()
function. However, it isAlmost every person out there confuses what that
compose()
function actually is. I have a dozen of examples. As well as many face to face discussions.What the
compose()
function actually does is it merges the descriptors using the standardized algorithm. We could rename the functionmerge()
instead. However... We can't use this word. In JavaScript it means object (deep/shallow) merging.But the word BLEND is unique to software development.
Pros:
blend()
word sounds exactly what thecompose()
function is actually doing - blends stamps.blend()
is shorter. :)))))))))))))Cons: