Re:Python Wheels Crosses 90%
by adrianN on Monday June 08, 2020 @01:41AM
(#23453911)
Maybe for software that runs on computers that you manage. But what about end-user software?
[ Parent
| on HN ]
Do 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?
Re:Python Wheels Crosses 90%
by dragonwriter on Monday June 08, 2020 @04:32AM
(#23454738)
Since 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.
For 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.
Re:Python Wheels Crosses 90%
by young_unixer on Monday June 08, 2020 @03:18AM
(#23454326)
The 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)
Isn'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.
You 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.