Re:Cinder: Instagram's performance-oriented fork of CPython
by sergiomattei on Wednesday May 05, 2021 @08:43AM
(#27049161)
To clear some confusion: both of you misunderstood my point.
I don't think Python's language readability is the problem.
The problem is CPython's core team shooting down any performance improvement for the sake of keeping the compiler source code readable.
Re:Cinder: Instagram's performance-oriented fork of CPython
by hitekker on Wednesday May 05, 2021 @09:25AM
(#27049520)
The last two discussions I recall on HN:
Re:Cinder: Instagram's performance-oriented fork of CPython
by throwaway894345 on Wednesday May 05, 2021 @06:15PM
(#27056507)
Mine is the top comment on that first link with 34 upvotes. :)
Re:Cinder: Instagram's performance-oriented fork of CPython
by throwaway894345 on Wednesday May 05, 2021 @10:07AM
(#27049980)
I did indeed misunderstand. Thanks for the clarification! :)
Re:Cinder: Instagram's performance-oriented fork of CPython
by mikepurvis on Wednesday May 05, 2021 @08:06AM
(#27048854)
Whl archives ship extracted, cacheable metadata, not the setup script.
Re:Cinder: Instagram's performance-oriented fork of CPython
by throwaway894345 on Wednesday May 05, 2021 @08:17AM
(#27048933)
Not everything is whl though.
I suspect one of the reasons packaging is so bad is because for each node on the dependency tree, you need to download and execute setup.py in order to discover the node’s direct dependencies, and to get the transitive dependencies you must download and execute the direct dependencies’ setup.py filles. Since these files aren’t idempotent, we can’t reliably cache the results (these scripts could return different sets of dependencies based on the environment or even the current time or anything else). This at least seems to be the reason all reproducible package managers are slow (by which I mean 30+ minutes to resolve dependency versions for a small non-toy project even if the resolved dependencies at their property versions are already cache to disk).