In practice, few people needed such complex querying and chaining. I think IFTT has a better metaphor ("if this, then that") which is much simpler but covers 80% of useful things.
In practice, few people needed such complex querying and chaining. I think IFTT has a better metaphor ("if this, then that") which is much simpler but covers 80% of useful things.
Absolutely.
OSCMS 2007 was hosted at Yahoo!, and it was one of the first developer conferences I made it to after moving to the Bay area. My takeaway from the session on Pipes was that it was a bit ... advanced (at least it was for me at that time). Pipes was not necessarily "forgettable", but it wasn't quite to the place it would induce radical inspiration. The inspiration kinda got lost in the bog of over-engineered complex details.
This seems to be a common trend among Yahoo's many assets: build almost-prototypes of platforms that absolutely ooze potential energy. But then waste that energy by stretching it in too many directions at once, not getting very far.
Visual programming is a guarantee of failure, unless your target users are electrical engineers. Fact.
I recall mashing up RSS feeds and using it to bypass various platform throttles.
It was awesome for fixing wonky feeds.
Love the UNIX metaphore and interface.
Pipes was the only Yahoo! product that really sang to me.
I think I've been relying on IFTTT too much lately. I may have to revisit Pipes.