Re:Learning Go as a Python Developer: The Good and the Bad
by smeagull on Monday July 18, 2022 @07:13PM
(#32145335)
If I did that I'd have no harddrive space left due to how large python dependencies are.
[ Parent
| on HN ]
Re:Learning Go as a Python Developer: The Good and the Bad
by Spivak on Monday July 18, 2022 @08:21PM
(#32145883)
Wat? What dependencies? I have right now 100 separate Python projects which each have their own venv, their own isolated dependencies, and their own isolated copy of Python itself and my code dir doesn’t even crack top 10 hard drive space.
Re:Learning Go as a Python Developer: The Good and the Bad
by Game_Ender on Monday July 18, 2022 @10:29PM
(#32146846)
Machine learning packages like
Tensorflow can result in GB size package directories.
Re:Learning Go as a Python Developer: The Good and the Bad
by stavros on Tuesday July 19, 2022 @08:00AM
(#32150314)
Yes, the biggest available library is big, that's hardly an argument though.
Re:Learning Go as a Python Developer: The Good and the Bad
by smeagull on Thursday July 21, 2022 @08:46AM
(#32178654)
A really common library that gets used in every project for common use-cases is big.
It's a very good argument.
Re:Learning Go as a Python Developer: The Good and the Bad
by stavros on Thursday July 21, 2022 @08:48AM
(#32178667)
No, saying "one common library is big" isn't a good way to show that "Python dependencies are big", which is what the initial claim was. Most libraries are tiny, and there's a very big one because it does many things. If Tensorflow were in JS it wouldn't be any smaller.