4 ms·
You could perhaps imagine web apps as a form of 2FA, half the app is on the client, and the other half is on the server and continually authenticating each othe
by chadcmulligan 2y ago
You could perhaps imagine web apps as a form of 2FA, half the app is on the client, and the other half is on the server and continually authenticating each other by communicating with each other.
There's no reason you can't do this with desktop apps, put a chunk of the functionality on the server and obtain security that way.
The trouble with web apps is compute and storage performance, for a web app you're limited by the browser - not so much for a desktop. Its not really an issue for a bingo card creator, it is if you're making blender or autocad.
- groestl 2y ago> half the app is on the client, and the other half is on the server and continually authenticating each other This is not what 2FA is.
- asdff 2y agoWhat did you have in mind with the browser being a limiting factor? It seems to me you can run stuff in the browser that makes use of all your local resources and can save things as well, considering tools like jupyter notebooks.
- qsort 2y ago> Its not really an issue for a bingo card creator, it is if you're making blender or autocad. This is obviously valid, but considering how powerful even low-end computers are these days, I'd say that most of the stuff we do on a computer is more like bingo card creator than blender or autocad. Software that is slow in spite of this is generally slow because it does a thousand network requests in the background. A 2009-era argument could have been that desktop apps are more respectful of your privacy, but that ship has long sailed due to pervasive telemetry, and it wasn't really ever true for mobile anyway.