Granting some application with a bundled ancient and insecure Electron build is insanity.
Granting some application with a bundled ancient and insecure library of any kind is bad. That is not a problem exclusive to Electron it applies to static builds of any application ever made.
Luckily there are plenty of native source code editors out there, for example Kate.
Okay but that’s not the point. You said, “Just load the wrapped website in a browser.” Some apps won’t function like that. The fact that alternatives exist is irrelevant to what I replied to.
Okay but that’s not the point. You said, “Just load the wrapped website in a browser.”
I replied to “it’s hard to do without them”. So yeah, opening wrapped websites in a browser for most Electron apps and using native alternatives for the rest is totally feasible and absolutely not beside the point.
Yeah, it’s feasible to do that. And? My point was that you can’t just rip out the web portion of an app and always expect it to work in a browser. That’s it. What you said is irrelevant in the sense that it has no effect on whether the web portion can run in a browser or not.
That works for some apps but not anything that needs access to the filesystem and/or devices. Things like VSCode or mod managers, etc.
Granting some application with a bundled ancient and insecure Electron build is insanity.
Luckily there are plenty of native source code editors out there, for example Kate.
Granting some application with a bundled ancient and insecure library of any kind is bad. That is not a problem exclusive to Electron it applies to static builds of any application ever made.
Okay but that’s not the point. You said, “Just load the wrapped website in a browser.” Some apps won’t function like that. The fact that alternatives exist is irrelevant to what I replied to.
I replied to “it’s hard to do without them”. So yeah, opening wrapped websites in a browser for most Electron apps and using native alternatives for the rest is totally feasible and absolutely not beside the point.
Yeah, it’s feasible to do that. And? My point was that you can’t just rip out the web portion of an app and always expect it to work in a browser. That’s it. What you said is irrelevant in the sense that it has no effect on whether the web portion can run in a browser or not.