| Problem with PWA:
Native access, Browser versioning and seperation of processes. 1. If when you ran a .net application all .net applications shared the same parent process that'd be a significant problem. 2. Many electron clients control their versions because there are bugs, quirks, removal of features, or other changes in chromium versions. Discord last time I checked is still on 56. 3. PWA's do not have native access. Discord requires that to spawn IPC communications with game overalys, which are another native process. PWA's are meant more for mobile, but even there you are of course, limited. Firefox and Safari would change the world if they actually cared about doing that. They're about market share, not about the technology anymore. Firefox was in a position of making it possible to simply ship the firefox binary, and you could add your js and css changes, effectively having the full firefox browser as your 'app'. Which means it could be triggered to auto-update like normal firefox, but still have your UI and act as a browser. Firefox abandoned that route and instead is focusing upon whatever Chrome impliments, like Custom Components. Safari also doesn't care about anything but linux and mac. |