2 ms·
That's absolutely not true for desktop GUI apps because so many of them are written in Electron these days. Even small desktop accessories carry their own copy
by pavlov 6y ago
That's absolutely not true for desktop GUI apps because so many of them are written in Electron these days.
Even small desktop accessories carry their own copy of the Electron and Chromium libraries, usually around 150 MB. It would be a tremendous improvement to use a shared browser engine for this, but developers are resistant.
- posix_me_less 6y agoShared browser engine or any other library would be ideal and in a single project a preferable way. But in practice it is hard to synchronize requirements of different applications, because they are different projects and different people on different schedules. 100 times 150 MB is still only 15GB, a minor part of hard drive, a very acceptable price for 100 functioning independent applications.
- pavlov 6y agoHow many of those apps are running simultaneously? Often quite a few. The memory footprint of the engine is larger than the code size on disk. Users may be wasting gigabytes of RAM on trivial desktop tools. The point of the web is to support multiple user agents rather than forcing the user to a specific browser. I don’t understand why that shouldn’t apply to web apps running on the desktop.
- posix_me_less 6y ago> The memory footprint of the engine is larger than the code size on disk. Users may be wasting gigabytes of RAM on trivial desktop tools. That may be the case. Usually it is not a problem, there is mmap and swap and unneeded parts are paged out of physical RAM. If it becomes a problem, one has to change tools or get more RAM.