Follow me on Twitter for my latest adventures!

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.
Follow me on Twitter for my latest adventures!

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.
Comments
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?
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.
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?!
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.
Heya i am for the first time here. I came across this board and I find It truly useful & it helped me out much. I hope to give something back and help others like you aided me.
Leave a new comment