3 ms·
Couldn't they rip-out the WebRTC stack - leaving out the RAM-hungry parts of Electron/Chromium/V8/etc that aren't relevant to desktop applications (e.g. aggress
by DaiPlusPlus 7y ago
Couldn't they rip-out the WebRTC stack - leaving out the RAM-hungry parts of Electron/Chromium/V8/etc that aren't relevant to desktop applications (e.g. aggressive in-memory caching, process isolation, etc)?
As much as we all have strong opinions about Electron, surely someone who is able to make a solidly built "DOM+CSS+JS+Optional extras" version of Electron would be make _bank_ overnight by servicing and consulting for it? I know lots of companies would love a build of Electron with a smaller attack-surface, for example.
- BiteCode_dev 7y agoThe WebRTC stack depends on: - the network code - the video and audio playing code - the video and audio capture code - the crypto code Making that generic is a huge task nobody will every do. So since you embed them, why no elso embed the UI code ? I mean, at this point...
- __s 7y agoNot to mention making that generic would want to be accepted upstream in order to have upstream maintain this interface