I get an error message (from the actual app, http://browserling.com/) - "No API resources availble for null group" (seems to be no matter which Browser/Version or URL I choose).
There appears to be several issues to work out. I've not been able to get a page rendered. I get "Nexus is down. Try again shortly." "No API for group null" and "You are not signed in!" when I am signed in.
I got to use it. It's basic for now but shows a lot of promise. A number of factors that you'd need to add for me to even consider using it:
- Bigger browser window
- More responsive UI. It shows a message saying a plugin was not run (flash) but it took forever to be able to click the X on the message to hide it and it locked up the browser (not my browser but the browser in the browser.)
- There was a lot of waiting in the queue and it suggested paid plan... but no paid plan available.
- I was able to access other parts of the machine, including the printing and devices section (usually visible when you right click the computer icon and click properties. You might want to lock down the machine a bit more.
I'm guessing you're aware of most of these.
The only other thing I'll say is that how are you dealing with the Windows licensing? You probably don't want to ignore dealing with that if you haven't yet as it could be painful in the future.
This is a very innovative project and I hope you pursue it regardless of yc funding or not. There's lots of Windows apps that would be useful to run in a browser :)
This marks the first time I have ever been represented as a purple robot. The person in front of me was a dinosaur, so I think it's only fair that they got to go first.
Great idea. I see this as a benefit for developers who do not have access to their own pc. Or to clients and/or qa who need to do a quick check.
Otherwise, developers can do everything that Browserling does and more with a combination of Virtual Machines, Multiple IEs, and Internet Explorer Collection, etc. Having developer tools is the key.
I think this could be successful because it lets people interact live with elements on the page. This is one thing that Adobe BrowserLab fails to do (http://forums.adobe.com/thread/725431?tstart=0 for example).
You may not want to answer this, but how will this service scale? Booting an individual VM for each user seems incredibly resource intensive.
Tried it out for IE6 and when the window loaded, someone else's site was up and I was unable to do anything while the counter ticked down. A bit concerning from a privacy standpoint. Maybe the machine fell over?
I had about the same; when switching to Firefox, it opened a new tab and before this was opened I was still able to look at an existing tab of someone else.
I entered the URL for a site I'm building, wanting to see if IE9 was going to screw me up (I'm still on WinXP), and I was sent to a queue.
My only real complaint about the queue is that you give absolutely no indication of how long the expected wait time will be. This would be reasonable, except for the countdown clock, which simply read 00:00 the whole time I was waiting.
When I got out of the queue, the countdown clock set itself to 01:30 (quick question: why the leading zero on the minute portion if it's only going to be a single digit value? Is it aesthetics? I actually liked it but I was just wondering...). Unfortunately, for the first 10-15 seconds or so, I was just faced with a blank screen, save for the border around what I assume should be my browserling. After waiting for these 10-15 seconds, I was told that my time was up. The countdown was still running down while this message was shown.
Going back to the queue, I'm assuming that the 1:30 I saw counting down on the other page is a standard time limit for a free user, so why can't you give me a reasonable estimate based on something like (users-in-queue * 90seconds) / number-of-available-machines-or-vms-or-whatever?
Sorry about that! When the API servers go down (these interface with our windows servers) it tells everybody in the queue "time's up" instead of a more informative message since we're using connection drops as a poor way of passing along the session expiry event.
first one when I search for "browsers screenshots"
EDIT : I can't get it to work neither on Firefox nor on Chrome. But I believe the difference is that we can click and use javascript on Ycombinator's version ? That can be usefull to test IE on a website's javascript. Eventhough using a framework like jquery should let us stop worring about that right ?
Interesting technology. I feel it creates more opportunity like your favorite IDE configured with SCM (say github) available right on your browser. Code as you go. No more setting / configuring the IDE more than once.
I know this. They use dnode (https://github.com/substack/dnode) for most of their inter-process/inter-browser communication, which uses socket.io for the web action.
Unfortunately 2 session timeouts, one missing route error, and now my seconds are ticking down while a rather bashful robot tells me my site is loading.
Good idea though - if you can get the pricing model to a point where it's appealing to my infrequent but bursty usage (and you make it reliable), I'd definitely be interested.
55 comments
[ 7.0 ms ] story [ 144 ms ] threadI'm using Chrome, as requested.
There appears to be several issues to work out. I've not been able to get a page rendered. I get "Nexus is down. Try again shortly." "No API for group null" and "You are not signed in!" when I am signed in.
- Bigger browser window
- More responsive UI. It shows a message saying a plugin was not run (flash) but it took forever to be able to click the X on the message to hide it and it locked up the browser (not my browser but the browser in the browser.)
- There was a lot of waiting in the queue and it suggested paid plan... but no paid plan available.
- I was able to access other parts of the machine, including the printing and devices section (usually visible when you right click the computer icon and click properties. You might want to lock down the machine a bit more.
I'm guessing you're aware of most of these.
The only other thing I'll say is that how are you dealing with the Windows licensing? You probably don't want to ignore dealing with that if you haven't yet as it could be painful in the future.
Overall, very interesting technology. Kudos!
To the creators of browserling, please don't take these negatives as criticism. It's a great idea and very ambitious, I am excited to use this site!
The toolbar is prefixed "http:// -- is there support for https? If not, is that on the roadmap?
Otherwise, developers can do everything that Browserling does and more with a combination of Virtual Machines, Multiple IEs, and Internet Explorer Collection, etc. Having developer tools is the key.
You may not want to answer this, but how will this service scale? Booting an individual VM for each user seems incredibly resource intensive.
(disclaimer: I interned on BrowserLab)
The lag is a bit too much, but other than that I think it's brilliant.
I entered the URL for a site I'm building, wanting to see if IE9 was going to screw me up (I'm still on WinXP), and I was sent to a queue.
My only real complaint about the queue is that you give absolutely no indication of how long the expected wait time will be. This would be reasonable, except for the countdown clock, which simply read 00:00 the whole time I was waiting.
When I got out of the queue, the countdown clock set itself to 01:30 (quick question: why the leading zero on the minute portion if it's only going to be a single digit value? Is it aesthetics? I actually liked it but I was just wondering...). Unfortunately, for the first 10-15 seconds or so, I was just faced with a blank screen, save for the border around what I assume should be my browserling. After waiting for these 10-15 seconds, I was told that my time was up. The countdown was still running down while this message was shown.
Going back to the queue, I'm assuming that the 1:30 I saw counting down on the other page is a standard time limit for a free user, so why can't you give me a reasonable estimate based on something like (users-in-queue * 90seconds) / number-of-available-machines-or-vms-or-whatever?
first one when I search for "browsers screenshots"
EDIT : I can't get it to work neither on Firefox nor on Chrome. But I believe the difference is that we can click and use javascript on Ycombinator's version ? That can be usefull to test IE on a website's javascript. Eventhough using a framework like jquery should let us stop worring about that right ?
Now i goto grok the stack vm code. ;-)
Good idea though - if you can get the pricing model to a point where it's appealing to my infrequent but bursty usage (and you make it reliable), I'd definitely be interested.