Correct me if I am wrong, but to an extent, isn't the memory bloat inherent to Chrome's sandboxing model? Having worked on a similar project, I firmly believe remote rendering is not only better speed wise but also efficiency wise. In some cases, might be better security wise, too.
Browsers are probably what I need keep open all the time along with other IDEs; and of the two, I'd prefer to teleport the Browser away to free up RAM (speak nothing of the battery). Right now, I see Firefox take up 75% of the available RAM starving other applications. Enabling swap only makes matters worse; and slows the PC to a crawl whenever page swaps to/from disk, which is usually the case when navigating between different IDE windows and the browser.
Given the amount of SaaS apps and the pace of its adoption across enterprises, Mighty, if it solves the problem it set out to, is likely to laugh all the way to the bank.
The thing is that RAM is really cheap. Right now on my machine Firefox is using 5GB of RAM, which at current prices would cost about 75¢/month amortized over three years. It seems hard to justify paying 40 times that amount for this service
You're not wrong with your commentary which is basically surmised by https://en.wikipedia.org/wiki/Parkinson%27s_law
> Chrome uses a ton of memory. Is this necessary?
Correct me if I am wrong, but to an extent, isn't the memory bloat inherent to Chrome's sandboxing model? Having worked on a similar project, I firmly believe remote rendering is not only better speed wise but also efficiency wise. In some cases, might be better security wise, too.
Browsers are probably what I need keep open all the time along with other IDEs; and of the two, I'd prefer to teleport the Browser away to free up RAM (speak nothing of the battery). Right now, I see Firefox take up 75% of the available RAM starving other applications. Enabling swap only makes matters worse; and slows the PC to a crawl whenever page swaps to/from disk, which is usually the case when navigating between different IDE windows and the browser.
Given the amount of SaaS apps and the pace of its adoption across enterprises, Mighty, if it solves the problem it set out to, is likely to laugh all the way to the bank.
Edit: The launch blog post is worth a read: https://blog.mightyapp.com/mightys-secret-plan-to-invent-the...