Hacker News new | ask | show | jobs
by ajxs 2401 days ago
> running an entirely seperate instance of an infamously memory hogging web browser

Without looking at the source-code: Doesn't this problem still exist, just in a different form? You're still running some kind of browser instance to render the UI, rather than using native methods.

2 comments

But you're using the browser already!
Yes, but this is the UI of a browser. Arguably it could be more efficient to do it this way as you can strip out some of the libraries used for the native rendering.
I don't see how. Those libraries are already loaded anyway because they're used by the OS and native apps.