> This is harder than it already being local, or apt-get install turning into apt-get source. Likely, if they find your app interesting they will keep using it

> This is harder than it already being local, or apt-get install turning into apt-get source. Likely, if they find your app interesting they will keep using it directly from your URL and end up at your mercy. You have the same issues with the centralized package distribution system you're pushing? You're reliant on a 3rd party. How many apt-get the source? Saving source on a front-end web app is as simple as clicking "Save As" in the browser and you get the bonus of not having to compile anything. It'll just work. > Your argument is analogous to a C programmer insisting that if one just follows the rules, C is just as expressive and safe as a higher level language. Not quite. You're simply not seeing the levels of abstraction present in your ecosystem because you're used to them. Centralized repositories, binaries, toolchains, etc. > "Web" implies executing code off of a third-party server. If you follow this logic, your apt-get example is executing binaries off a 3rd party server. You sure you want to go there?