3 ms·
Maybe for software that runs on computers that you manage. But what about end-user software?
by adrianN 6y ago
Maybe for software that runs on computers that you manage. But what about end-user software?
- spenczar5 6y agoIsn't that still broken if code is dynamically linked? If you don't control the end-user platform, you're out of luck anyway; static builds neither help nor hurt.
- caymanjim 6y agoDo you think it's easier for end-users to update Python packages on their own, or just install the latest version of the app that they know about?
- drran 6y agoFor Linux, it's easier to just perform update. For half-developed OS'es, it's easier to download installer, then Next, Next, Agree, Next, No, Next, wait, Finish.
- young_unixer 6y agoThe irony being that in the fully developed OS I experience: - Outdated packages - Having to build from source when the package is not in the repos - Failed builds for no good reason - Unability to have many versions of that same packages - having to install log(n) build tools if I want to build n packages - etc while in half-developed OS'es everything just works (application-wise, at least)
- dragonwriter 6y agoSince either can be automated in the distributed software itself, I'd say they are both equally easy for the end-user, if the developer really cares.
- pas 6y agoYou can pre-build the static bin for the target platforms, you know exactly what are the bits in the blob on the user's box, and you can ship a binary diff and do incremental evergreen auto-updates. Probably faster and less brittle than testing/shipping and keeping Python up to date on the user's box.