Yahoo Pipes End-Of-life Announcement
141–150 of 184 posts
Re: Yahoo Pipes End-Of-life Announcement
#142pipes 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.
Pipes has long been a sort of monument to the faith of a bygone age -- the first flush of Web 2.0 optimism, when standard formats and open APIs were going to let us mix and match and mash up services of all kinds at will. That faith is dead now, of course, scoured from the earth by walled gardens and VC money. But like Catholics in Elizabethan England, some of us quietly tend our secret shrines and pray for its retur…
> Bosworth advocated an open model for data.(...) Imagine if you can query any data that is available anywhere in the world. Bosworth said that what this requires is a single, simple, open wire format for items. The format needs to be simple for any P programmer to deliver and any JavaScript programmer to consume. He also pointed out that "complex things tend to break and simple things tend to work." Google has the simplest query language in the world. There is no structure and no syntax. (my note: at that time Bosworth was VP of Product Management at Google)
That is all dead now.
Re: Yahoo Pipes End-Of-life Announcement
#143Netflix does not believe in RSS, even though their Influencer content is not behind a subwall. I use Pipes to parse Netflix's json content and then turn it into a feed. I even created a Pipe that took any influencer ID and automatically created an RSS feed.
The idea was started because Daniel Tunkelang of Netflix was very anti RSS. I showed him, but alas, no more.
I never figured out how to use IFTTT. How can you grab any content from the web, like Netflix's json content? There is no HTTP input as far as I can tell.
Re: Yahoo Pipes End-Of-life Announcement
#144Pipes was the first service I ever owned from an ops perspective (circa 2008). We had two clusters, one on each coast. I thought we had capacity to take one offline to do a full upgrade, turns out we didn't. By the time I turned the west coast back online, the east coast was failing health checks, and the LB failed everything over to the west coast, which then proceeded to be overloaded, and everything flipped back t…
Re: Yahoo Pipes End-Of-life Announcement
#145Earlier quoted context omitted.
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'm still upset by the fact that MeeGo/Maemo was killed, and Nokia sold to Microsoft. The N9 was still the best phone I've ever used, and it's UX ideas are still the simplest and most effective way of using a phone, and yet no one else has implemented it.
Re: Yahoo Pipes End-Of-life Announcement
#146pipes 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.
Pipes has long been a sort of monument to the faith of a bygone age -- the first flush of Web 2.0 optimism, when standard formats and open APIs were going to let us mix and match and mash up services of all kinds at will. That faith is dead now, of course, scoured from the earth by walled gardens and VC money. But like Catholics in Elizabethan England, some of us quietly tend our secret shrines and pray for its retur…
Re: Yahoo Pipes End-Of-life Announcement
#147Earlier 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?
Instead of closing it down, releasing the source and giving it to the community could breath live into it. I remember being blown away by it, the fact that it was neglected and just kept on says a lot about it's good design.
Re: Yahoo Pipes End-Of-life Announcement
#148Yahoo 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…
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.78.5...
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.78....
ConMan: A Visual Programming Language for Interactive Graphics (1988)
Abstract
Traditionally, interactive applications have been difficult to build, modify and extend. These integrated applications provide bounded functionality, have a single thread of control and a fixed user interface that must anticipate every-thing the user will need. Current workstations allow several processes to share the screen. With proper communication between processes, it is possible to escape previous models for application development and evolution. ConMan is a high-level visual language we use on an IRIS workstation that lets users dynamically build and modify graphics applications. To do this, a system designer disintegrates complex applications into modular components. By interactively connecting simple components, the user constructs a complete graphics application that matches the needs of a task. A connection manager controls the flow of data between individual components. As a result, we replace the usual user-machine dialog with a dynamic live performance that is orchestrated by the user.
Re: Yahoo Pipes End-Of-life Announcement
#149Hats off to all those that worked on the product - great to see it remembered so fondly.
Re: Yahoo Pipes End-Of-life Announcement
#150Earlier quoted context omitted.
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...
Here in Brazil Elop effect was interesting: it was VERY obvious, yet noone here knows who the hell Elop is.
To put it simple: When Elop released that stupid memo, Nokia had 67% of Brazil smartphone market share, and the share was still rising, and Nokia utterly dominated in the non-smartphone market too. Right after Elop memo, the first thing that happened is that suddenly the communities died (although Nokia store DID suck, there was at least in Brazil a vibrant freeware app community that shared stuff in forums), then just some months later you could not find phones for sale, even new models, because the import companies DID heard of Elop memo, and decided to not risk importing the phones, even if shopkeepers still wanted it.
The end result was funny: Elop nuking of Symbian was so hard, that in Brazil other smartphones could not keep up for a while, and we temporarily had a decrease in smartphone use, and a increase in feature phone use, and that increase came mostly from truly crap chinese companies, because not even Nokia feature phones could be found in stores anymore.