Post #2340698
2026-05-06 14:11 UTC
@dalias@hachyderm.io @arclight@oldbytes.space
I think that's an important and useful distinction. There's a fundamental difference between
"You search, find and download a library to use with your code"; and
"You follow an intro tutorial and the tool chain pulls it down as a secondary dependency without you even knowing what it is, or that it was going to happen."
Replies (1)
-
@arclight@oldbytes.space 2026-05-06 15:33
@jannem@fosstodon.org @dalias@hachyderm.io Agreed. Compare the review and configuration management burden of say, including the PCRE library into a compiled C project vs shipping a Python application with a full Python virtual environment. Even the cascade of dependencies from a simple requirements.txt file can be a huge amount of code. Until you start doing strict configuration management you don't see the burden most interpreted codes put on you. Nobody wants to hear that Python, R, etc. is not fit for use in a high integrity environment, at least not in the way that 99% of developers use it.