3 ms·

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

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

psadri 11y ago
Correct and thanks for those links. Pipes was influenced by unix pipes (hence the name). The UI was influenced by National Instrument's LabView and Apple's Automator. I wish Pipes was launched in the age of containers (e.g. Docker). We had the idea of one click deployment to what we today call a container.
empyrical 11y ago
I really hope there's a new service that can pick up where Pipes left off, it was a huge shame how it fizzled out at yahoo.
DonHopkins 11y ago
Paul Haberli made ConMan on SGI workstations: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.78.5331 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.5331&rep=rep1&type=pdf 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.

psadri 11y ago

Correct and thanks for those links. Pipes was influenced by unix pipes (hence the name). The UI was influenced by National Instrument's LabView and Apple's Automator. I wish Pipes was launched in the age of containers (e.g. Docker). We had the idea of one click deployment to what we today call a container.

empyrical 11y ago

I really hope there's a new service that can pick up where Pipes left off, it was a huge shame how it fizzled out at yahoo.

DonHopkins 11y ago

Paul Haberli made ConMan on SGI workstations: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.78.5331 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.5331&rep=rep1&type=pdf 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.