Webshell.io: the shell for scripting and combining APIs in Javascript
11–20 of 34 posts
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#12This does seem to need more of a sell. Intuitively it feels cool - but then I’m not sure of what I’d use it for. My first thought was that it’s the other half of the https://www.webscript.io/
The idea is more to be an IFTTT/Zapier for developers but without limited inputs and outputs by Graphical User Interface. With the expressiviy of an all language as Javascript and a console interface to explore API and check easilty data response, developers may not be limited when combining APIs and make exactly what they wanted to do. But Webscript.io is nice too, some similarities but not the same usefulness, not…
Is a great description - a very clear value statement there.
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#13Cool interface but I'm not sure what sort of value you're going for here. Is it a set of APIs that make it easier to get stuff done in a repl? If so, it doesn't seem more useful than console so far (looking at the Google Maps and HTTP call examples). Or is it a lightweight IDE -- if so, would this be better done as a browser extension that could circumvent security restrictions? (and also operate on any document, inc…
Our idea is to help web and mobile developers - to sandbox API workflow (server-side APIs and/or client-side APIs) into the REPL interface "prototype" - and then create a new API based on this API workflow(or "prototype") - use this new API in production into their own application and share it with other developers we want to bring fast API discovery and exploration, easy multiple API mashups or scripting, then new A…
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#14Hey I think it's a great idea. I'm a developer evangelist at TokBox and I love playing around with APIs so I think I'll be using this tool quite often. Personally, I think you can create alot more value by opening up a platform so that API companies can write their own interactions into WebShell. This way it's more scalable and we'll be able to do cool mashups with other APIs.
But for the moment you can share with us your API by sharing a WADL of it and make a pull-request on our Github http://github.com/webshell
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#15Funny there is already a (less advanced) open source application that does this... with the same name :) https://github.com/hbbio/webshell Disclaimer: I'm the author of the open source webshell.
We would be glad to talk with you.
Contact us team[at]webshell.io if you are interested :)
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#16Earlier quoted context omitted.
The idea is more to be an IFTTT/Zapier for developers but without limited inputs and outputs by Graphical User Interface. With the expressiviy of an all language as Javascript and a console interface to explore API and check easilty data response, developers may not be limited when combining APIs and make exactly what they wanted to do. But Webscript.io is nice too, some similarities but not the same usefulness, not…
> The idea is more to be an IFTTT/Zapier for developers but without limited inputs and outputs by Graphical User Interface. Is a great description - a very clear value statement there.
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#17Cool interface but I'm not sure what sort of value you're going for here. Is it a set of APIs that make it easier to get stuff done in a repl? If so, it doesn't seem more useful than console so far (looking at the Google Maps and HTTP call examples). Or is it a lightweight IDE -- if so, would this be better done as a browser extension that could circumvent security restrictions? (and also operate on any document, inc…
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#18Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#19Cool interface but I'm not sure what sort of value you're going for here. Is it a set of APIs that make it easier to get stuff done in a repl? If so, it doesn't seem more useful than console so far (looking at the Google Maps and HTTP call examples). Or is it a lightweight IDE -- if so, would this be better done as a browser extension that could circumvent security restrictions? (and also operate on any document, inc…
Our idea is to help web and mobile developers - to sandbox API workflow (server-side APIs and/or client-side APIs) into the REPL interface "prototype" - and then create a new API based on this API workflow(or "prototype") - use this new API in production into their own application and share it with other developers we want to bring fast API discovery and exploration, easy multiple API mashups or scripting, then new A…
What do you mean by "to sandbox API workflow"?
Why should I get a script from your server in my production application instead of serving it myself? It's one dependency more.
The only real value i see is the fact of having a library that gives me some syntactic sugar to query third party apis (like twitter, foursquare, gmaps, ...) but for that I would need only a very little part of your service, and maybe I'd prefer an open source solution.
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#20Earlier quoted context omitted.
Our idea is to help web and mobile developers - to sandbox API workflow (server-side APIs and/or client-side APIs) into the REPL interface "prototype" - and then create a new API based on this API workflow(or "prototype") - use this new API in production into their own application and share it with other developers we want to bring fast API discovery and exploration, easy multiple API mashups or scripting, then new A…
Ok, but why should I use your service instead of writing JavaScript in Vim? Apart from the fact of seeing the output more or less on the fly the result is the same (but I'll never abandon my editor for that). What do you mean by "to sandbox API workflow"? Why should I get a script from your server in my production application instead of serving it myself? It's one dependency more. The only real value i see is the fac…