Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Yahoo Pipes End-Of-life Announcement

pipes.yqlblog.net

Post reply on HN
Print view View original

101–110 of 184 posts

Re: Yahoo Pipes End-Of-life Announcement

#101

Post by olviko »

basch wrote: post #30
psadri wrote: post #15

Earlier quoted context omitted.

IFTTT and Zapier are spiritual successors to Pipes, although their focus is on APIs vs feeds. Maybe start a new, open source version of Pipes?

It really would be oh so nice to have something that can ingest RSS and Tweets and then apply filters to them while visualizing the logic through a graphical interface. Maybe even some fuzzy machine learning to use in building filters. Some more advanced dupe technology would go a long way. People would be building their own techmemes in no time. You could build ranking systems that award bonus points if something li…

Checkout https://github.com/olviko/RssPercolator

Pipes would often get blocked by 3rd party data providers, which motivated me to roll my own library.

No graphical interface. Personally, I found Y! Pipes UI hard to work with when I needed to build large pipelines.

Re: Yahoo Pipes End-Of-life Announcement

#102

Post by zacharycohn »

bryanh wrote: post #49

Aw man - that is sad. We at Zapier took great inspiration from Pipes, it was such a cool and powerful product! It was a shame to see it languish. I'd sure love to pick the brain of anyone formerly involved in the project - it seems like there is a lot we could learn from the trail it blazed. My email in profile, obligatory beers/coffee/etc. offer.

You guys are fantastic. I use Zapier for several of my organizations and companies, and I cannot understate how incredible of a service you guys have created. My only wish would be for a paid tier between 100 and 3000. If I went hog-wild and did everything I want to do, I'd probably use 200-300 a month. I would love to pay for that. But there's some loss-aversion psychology happening that makes me not want to pay for 3000 if I know I'll only use 300.

I'd give you my cc number right now if you did a 1000 zaps at $10/m.

That being said - you know your business better than I do. If it would hurt conversions of $20/m more than it would help, I get that. :)

<3 you guys though.

Re: Yahoo Pipes End-Of-life Announcement

#103

Post by mikeknoop »

zacharycohn wrote: post #102
bryanh wrote: post #49

Aw man - that is sad. We at Zapier took great inspiration from Pipes, it was such a cool and powerful product! It was a shame to see it languish. I'd sure love to pick the brain of anyone formerly involved in the project - it seems like there is a lot we could learn from the trail it blazed. My email in profile, obligatory beers/coffee/etc. offer.

You guys are fantastic. I use Zapier for several of my organizations and companies, and I cannot understate how incredible of a service you guys have created. My only wish would be for a paid tier between 100 and 3000. If I went hog-wild and did everything I want to do, I'd probably use 200-300 a month. I would love to pay for that. But there's some loss-aversion psychology happening that makes me not want to pay for…

Thanks for this Zach, we keep re-evaluating and running pricing tests, and this plays into that a bit. Reach out anytime if you need help!

Re: Yahoo Pipes End-Of-life Announcement

#104

Post by sirkneeland »

bsder wrote: post #99
smacktoward wrote: post #29

Earlier quoted context omitted.

> It took a lot of active mismanagement and folly to keep Pipes from living up to its promise. I feel like this unique blend will be Yahoo's lasting contribution to the field of management theory.

DEC/Compaq/HP is really hard to top in the area of mismanagement.

Don't forget Nokia. Going from #1 in a market to doing so badly that you exit the market--and all in the span of 3 years--is something to behold.

Re: Yahoo Pipes End-Of-life Announcement

#105

Post by edho »

psadri wrote: post #6

pipes creator here: sad to see pipes shutdown. i am surprised it lasted this long -- it was abandoned years ago. on the positive side, it is nice to see it mentioned in the same sentence as y! maps which used to be a big deal back in the day.

Thanks Pasha for letting me be a part of your brilliant idea.

Re: Yahoo Pipes End-Of-life Announcement

#106

Post by cehlen »

smacktoward wrote: post #62
georgemonck wrote: post #50

Earlier quoted context omitted.

It took a lot of active mismanagement and folly to keep Pipes from living up to its promise. I would love to read a blog post about how exactly it was mismanaged. It would be great for others to learn lessons from the mistakes.

The first rule of Mismanagement Club is you never talk about how you got into Mismanagement Club.

Love the reference!

Re: Yahoo Pipes End-Of-life Announcement

#107

Post by hippiefahrzeug »

sirkneeland wrote: post #104
bsder wrote: post #99

Earlier quoted context omitted.

DEC/Compaq/HP is really hard to top in the area of mismanagement.

Don't forget Nokia. Going from #1 in a market to doing so badly that you exit the market--and all in the span of 3 years--is something to behold.

good one. it's what one famous blogger calls the 'elop effect': http://communities-dominate.blogs.com/brands/2011/08/coining...

Re: Yahoo Pipes End-Of-life Announcement

#108

Post by denimboy »

Yahoo pipes was obviously influenced by UNIX pipes and as such is one of the best demonstrations of flow based programming to date. I really loved Yahoo pipes and it influenced the way I think.

Pipes was a basic web "agent". It made basic programming available to the everyman much like HyperCard. Perhaps is just needed a runtime UI that matched the excellence of its design time interface.

Yahoo is focussing on mobile yet here they had this custom agent building tool that could easily be re-purposed to mobile to make a killer platform for Yahoo users.

Hopefully they will opensource the first generation perl version.

Some of my favourite flow based programming links follow.

Surprised nobody has mentioned noflow node.js workflows:

  https://github.com/noflo/noflo
Also this (untested) will convert your yahoo pipes into Node.js

  https://github.com/neyric/pipes2js
and this one (also untested) will do the same in python:

  https://github.com/ggaughan/pipe2py
There is also python pypes which has a yahoo pipes like frontend with a stackless based backend.

  http://pyvideo.org/video/400/pycon-2011--large-scale-data-conditioning--amp--p
  https://github.com/fullscale/pypes
Other python flow based programming tools

  https://wiki.python.org/moin/FlowBasedProgramming
  http://www.kamaelia.org/Home.html (BBC research)
  http://www.ruffus.org.uk/index.html
Wireit is a javascript pipes like frontend

  http://neyric.github.io/wireit/docs/
As you can see I loved pipes and I can

Re: Yahoo Pipes End-Of-life Announcement

#109

Post by gcb0 »

sirkneeland wrote: post #104
bsder wrote: post #99

Earlier quoted context omitted.

DEC/Compaq/HP is really hard to top in the area of mismanagement.

Don't forget Nokia. Going from #1 in a market to doing so badly that you exit the market--and all in the span of 3 years--is something to behold.

i think nokia is more about lack of executive vision/market knowledge. The other examples are more about middle management, besides the executive lack of vision and bean counting.

Re: Yahoo Pipes End-Of-life Announcement

#110

Post by edho »

idlewords wrote: post #19

I worked on Pipes briefly, shortly after it launched. It was really two distinct products rolled into one. The visual interface was groundbreaking and stunning-I think half my team was hired on the strength of that demo. No one could believe Javascript could do that. The backend was an extremely useful tool for munging RSS feeds. With any kind of support, or even benign neglect, the product would have been successful…

It was really great to work with you. During the post-launch chaos, it was life saver that you didn't have your hair on fire like the rest of us :)

Jonathan Trevor's Javascript was out of this world amazing for the time.

Post reply on HN