5 ms·
> I don't think you remember how the yahoo pipes worked. True, I learned about it when it was already dead, but thought the goal was similar to the stuff Zapie
by zeptomu 9y ago
> I don't think you remember how the yahoo pipes worked.
True, I learned about it when it was already dead, but thought the goal was similar to the stuff Zapier offers and I would really like to try it. Not to automate stuff, but to checkout the visual editor.
- fiatjaf 9y agoOh, Zapier is a programmer's nightmare.
- robbiemitchell 9y agoWhy/how so?
- jameskegel 9y agoThat's an odd response. Why do you feel that way?
- bryanh 9y agoFunny you say that -- engineers are one of Zapier's best customer personas. Quicker and easier to implement functionality than deploying code to the cloud. Plus, non-engineers can take over maintenance so engineers can work on more interesting things. We also have code/scripting steps -- https://zapier.com/help/code/ https://zapier.com/help/code/ or https://zapier.com/help/code-python/ https://zapier.com/help/code-python/.
- gsvclass 9y agoI work on Webmatr which is also for building integrations except its with Javascript code. The entire platform runs of API Specs (Swagger, Open API). I just posted it on Show HN https://news.ycombinator.com/item?id=14469734 https://news.ycombinator.com/item?id=14469734 or the direct link https://webmatr.com https://webmatr.com
- onli 9y agoSome screenshots from old Yahoo pipes that show a bit how that worked: https://imgur.com/a/p6uf0 https://imgur.com/a/p6uf0
- LoSboccacc 9y agoThe pipes goal was to transform data upon a pull, not move data on triggers. The client was likely a reader, while those event system mainly push to api.