Webshell.io

Interacting and exploring APIs is either the newest fad or a gold rush for new business, but one of the biggest things stopping me from using them is integration into my existing stable tools. webshell.io is another service which is hosting your code on an external service, leaving you vulnerable to fluctuations in their uptime or stability as a company. There may be new opportunities in turning this into a desktop application.

Re: Webshell.io

#6

Post by mehdim » Mon, Dec 24, 2012, 1:57 AM UTC

NinetyNine wrote: post #5

Interacting and exploring APIs is either the newest fad or a gold rush for new business, but one of the biggest things stopping me from using them is integration into my existing stable tools. webshell.io is another service which is hosting your code on an external service, leaving you vulnerable to fluctuations in their uptime or stability as a company. There may be new opportunities in turning this into a desktop a…

But what would be the business model for such a desktop app?

Re: Webshell.io

#7

Post by gojomo » Mon, Dec 24, 2012, 2:02 AM UTC

Finally, a shell that has the past trail off below (revchron/blog-style) rather than up above (typewriter/terminal-style)!

Re: Webshell.io

#8

Post by mehdim » Mon, Dec 24, 2012, 2:03 AM UTC

FarhadG wrote: post #3

[deleted] wrote: post #2

[deleted]

what other respectable platforms do you know of that offer this service?

what kind of service are you talking about exactly?

Re: Webshell.io

#9

Post by primaryobjects » Mon, Dec 24, 2012, 2:08 AM UTC

I played with it @ http://webshell.io/prototype/Njc5Z/7

It seems to work. This uses a REST service I recently wrote in node.js + mongodb.

Edit:

14 people click the link and hit Run, but no one changes the text? Come on. I wrote a second little app to track this at http://webshell.io/prototype/Njc5Z/8 just keep clicking Run to see it update, as people run the original app and hopefully enter their name or something.

Re: Webshell.io

#10

Post by sentiental » Mon, Dec 24, 2012, 2:13 AM UTC

I appreciate the technical rigor required to make this kind of service stable and safe, but I am worried about the usefulness of the product / who would use it. Building APIs into my own abstractions in a real web application basically means I'll never use this myself. A more casual developer may use this to build simple mashups, or maybe hack out something for a hackathon, but beyond that why would I go through the trouble of figuring out how to integrate webshell with my own codebase? NinetyNine already mentioned this, but now I'm adding a new single point of failure and another web request, so I'm not quite sure how big the benefit is exactly.

Maybe it'll turn out that there's a huge need for some intermediate between IFTTT and vanilla API use, but I'm having a hard time seeing when.