4 ms·

The problem with Yahoo Pipes was that it was over-optimized for complex dataflows. It was possible to do things like "find all Flickr photos from user, filter b

The problem with Yahoo Pipes was that it was over-optimized for complex dataflows. It was possible to do things like "find all Flickr photos from user, filter by tag and display on a map by location taken". The result was this crazy programming GUI that resembled Labview. 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.

sabat 14y ago
I agree with you that IFTTT and Zapier are simpler solutions to more common needs, but man, Pipes is really powerful. It's more like a language than an automation framework. I don't know if it will ever make any money, but it's a hell of service.
- teaneedz 14y ago
  Long before IFTTT, Pipes was an excellent solution for various social media needs. 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.
shawnee_ 14y ago
... over-optimized for complex dataflows 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.
toyg 14y ago
> this crazy programming GUI that resembled Labview Visual programming is a guarantee of failure, unless your target users are electrical engineers. Fact.

sabat 14y ago

I agree with you that IFTTT and Zapier are simpler solutions to more common needs, but man, Pipes is really powerful. It's more like a language than an automation framework. I don't know if it will ever make any money, but it's a hell of service.

teaneedz 14y ago
Long before IFTTT, Pipes was an excellent solution for various social media needs. 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.

shawnee_ 14y ago

... over-optimized for complex dataflows 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.

toyg 14y ago

> this crazy programming GUI that resembled Labview Visual programming is a guarantee of failure, unless your target users are electrical engineers. Fact.