HN user

ajitk

285 karma
Posts7
Comments53
View on HN

Ajit from BrowserBox team here.

The core premise of BrowserBox and Mighty is similar - virtualize and run browsers on the server. Mighty is desktop app meant for end users. BrowserBox's API is for developers who can integrate it into apps or build custom apps using the platform. In the long run, one can potentially build a Mighty like app using BBX APIs. It is still early days and looking for active feedback from the community to see where it can go.

Thanks for your kind words. The stack is a mix of both. Browser runs on the server and sends updates to the client via websocket. Then it is painted on the client. On the client-side a part of noVNC js library is used to capture input and is sent to the browser running on the server.

Thanks for the great feedback. :)

Getting started would certainly be much simple when using screenshot or page HTML for comparison. Sieve could do that too! More work needs to be done to make startup faster.

On the other hand having filtered text provides multiple advantages. The filtering becomes accurate. It can be used to compute rules to take conditional actions. Notifications delivery via email and SMS would make more sense as well.

Running a browser on server enables another cool function. User could record macro and run the macro when text satisfied a pre-condition.

Edit: typo

> This puts less emphasis on "looking useful" as individuals and more on championing tasks to see their completion.

This is a very good approach. Separating task and people is key to getting things done. When things are getting tough for an individual, the team can rally behind.

I like it. Saw a similar approach in Firebug's domplate. dom-o looks cleaner.

I really like the pitch to "Reduce the number of moving parts" at the cost of small learning curve.