3 ms·
I don't see what the big issue with installing vs. not-installing is. When you start an app you copy code into RAM and then start executing it. What does it mat
by hn3333 6y ago
I don't see what the big issue with installing vs. not-installing is. When you start an app you copy code into RAM and then start executing it. What does it matter if the code is coming from your hard disk or from a webserver.
Secondly, of course the browser is like an operating system. It's a virtual machine abstracting away the underlying machine for security (a point the author completely forgot) and convenience reasons. And it's great at that.
What I personally dislike is the tooling available for modern web development. I neither particularly like the programming languages nor the frameworks and tools. Actually some of the setups I've seen do make me want to throw up a bit, too, that's why I am a happy native programmer (c++ and swift) most of the time!
- Xelbair 6y ago>I don't see what the big issue with installing vs. not-installing is. When you start an app you copy code into RAM and then start executing it. What does it matter if the code is coming from your hard disk or from a webserver. Persistence, and idempotency. Code you run from your local hard drive will work as expected every time you run it. Code grabbed from remote repository(website) might, and usually will, be updated/changed and it might break your workflow. It might not exist anymore.
- jacquesm 6y agoAnd the simple fact that it is still there tomorrow morning even if the 'service' decides to shut down.