Art by James Halliday.

1. We run the browsers on our servers.
2. You use the browsers from the graphical web console.
3. If the servers are full, you wait in the queue.

Try Browserling!


January 29, 2012, 23:35

Browserling is cool stuff. It feels sluggish, though, compared to a browser running locally.

I wonder what the bottleneck is and if it could be improved?

January 29, 2012, 23:59

Latency between the browser and servers. Plus encoding latency. Plus it's VNC, which is slow itself. It will get faster when I write a rdesktop implementation.

January 30, 2012, 12:41

Is there any particular reason why browserling only supports running browsers, apart from its name?

It seems like it would be just as easy to run other software in the browserling cloud?!

January 30, 2012, 14:04

See Announcement: I am doing a startup - StackVM! We built Browserling on top of StackVM. So Browserling can actually run any software. We have planned building a general application product, where you can use any software, but I have no idea when we'll get to that.

Leave a new comment

(why do I need your e-mail?)

(Your twitter name, if you have one. (I'm @pkrumins, btw.))

Type the word "0day_308": (just to make sure you're a human)

Please preview the comment before submitting to make sure it's OK.