type that for me faster!
Webshell.io: the shell for scripting and combining APIs in Javascript
21–30 of 34 posts
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#22Cool 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…
"Currently, you are in a shell that allow you to program the web in Javascript, Coffeescript or Typescript!" is an unnecessary detail. Just say "javascript* repl" and "*also runs coffeescript & typescript" at the bottom of the page.
I don't think the byline is working. I do a lot of front end work and have used a lot of these apis. "the shell for combining web apis" isn't putting a clear image into my mind. I don't know what it means to "combine web apis", nor do I know why I'd need a shell for it. Something like "the easiest way to work with popular web APIs" might be better--even though it is less technically accurate, it has a few advantages.
- it gives me a concrete idea that my mind can latch onto
- it piques my curiosity. "oh neat. why is this the easiest way to do XYZ?"
- it gives me a framework from which I can evaluate the rest of the page.Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#23Seriously, if you sold this as software that I could run anywhere, it would absolutely make my day. The libraries you guys have written are seriously impressive.
You could use this kind of technology for a more meaningful way to teach code - when you're done, you've written yourself a website.
Also, providing an external "API to rule them all" would be pretty cool, as well.
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#24Earlier 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…
It would be impossible to make a lib which maintain all third party APIs (arround 8000 today), it’s for that we made it as a platform where everything is always working.
Please note that Webshell is an API too, and you can call scripts as a REST/JSON API.
“Sandbox API workflow” : we have a REPL prototyping part for helping you to see very fast a result of API scripting results, as for server side API (Facebook, Spotify...) as for Client side (GoogleMaps, Youtube player etc...)
After you have two choices.
- Make it again by yourself, with the different API protocols, Oauth1.0 or Oauth2.0 , manage rate limits and keep an eye for maintenance on all your APIs in your application.
- Or push the “create API” button on top right of the Webshell prototyping REPL, so generating a new API of your mashup, use it in production and share it with other developers which would like to use it too.
Our job is to keep an eye for you on API maintenance, easy Oauth integration, APIkeys and rate limit management, analytics. We will be implement each feature step by step during the public beta.
Dependancy? We are an API like other APIs. We behave like Back-end-as-as Service as Parse for example. You could do it yourself to not be dependant, but if you implement it fast for your application, with lot of integrated tools, you will keep it in production.
You can see us as a kind of API-as-a-service backend... ;)
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#25I want a self-hosted version. Badly. Seriously, if you sold this as software that I could run anywhere, it would absolutely make my day. The libraries you guys have written are seriously impressive. You could use this kind of technology for a more meaningful way to teach code - when you're done, you've written yourself a website. Also, providing an external "API to rule them all" would be pretty cool, as well.
In our doc , you can read how to already use it on webshell.io/docs/reference
"In the programmable web where APIs lie,
One shell to rule them all, one shell to find them,
One shell to bring them all and in the cloud bind them"
;)Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#26Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#27Earlier quoted context omitted.
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…
You can use it as an IDE but it’s not the Webshell’s job ! Our job is to make an “API mashup factory” for people which want to make fast applications based on APIs. It would be impossible to make a lib which maintain all third party APIs (arround 8000 today), it’s for that we made it as a platform where everything is always working. Please note that Webshell is an API too, and you can call scripts as a REST/JSON API.…
Plainly, show, don't tell.
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#28Earlier quoted context omitted.
You can use it as an IDE but it’s not the Webshell’s job ! Our job is to make an “API mashup factory” for people which want to make fast applications based on APIs. It would be impossible to make a lib which maintain all third party APIs (arround 8000 today), it’s for that we made it as a platform where everything is always working. Please note that Webshell is an API too, and you can call scripts as a REST/JSON API.…
I think you need more examples of something complex that is made easily accessible. And show some of the advantage involved in using you as an API around third-party APIs. Plainly, show, don't tell.
You're definitively right.
Follow us, more examples soon.
Thank you for your advise.
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#29Nitpick: "example" is misspelled as "exemple" a bunch of places.
Re: Webshell.io: the shell for scripting and combining APIs in Javascript
#30Earlier 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…
some feedback: The homepage is visually cluttered. it took me a while just to parse the page and figure out what I'm supposed to do. even now that I do know what the page is about, my eyes still don't know where to look. "Currently, you are in a shell that allow you to program the web in Javascript, Coffeescript or Typescript!" is an unnecessary detail. Just say "javascript* repl" and "*also runs coffeescript & types…