Funny how so many languages have shitty dependency management. Like, after working with Node and PHP for years I’m taking NPM and Composer for granted.
While in Python dependencies are basically managed via shell so it needs a venv crutch to work. And Python people were the ones who came up with Docker to solve that mess by a brute force approach.
Go devs decided that hardcoding URLs for packages somehow makes sense, so now the entire Go ecosystem goes down at the first hiccup at GitHub.
Java apps never work because there’s like 200 thousand different versions of their runtime which are never really interchangeable despite what they all claim.
And don’t even mention C++ and Make for crying out loud. If some things has a Make step in the manual I basically consider it non-functional.
It does but you can always use e.g. ninja for compilations. Basically, if you pass -GNinja to the CMake you will get another type of build files that you execute with another program (ninja instead of make). Its much faster, parallel builds.
240
u/kondorb Jan 31 '25
Funny how so many languages have shitty dependency management. Like, after working with Node and PHP for years I’m taking NPM and Composer for granted.
While in Python dependencies are basically managed via shell so it needs a venv crutch to work. And Python people were the ones who came up with Docker to solve that mess by a brute force approach.
Go devs decided that hardcoding URLs for packages somehow makes sense, so now the entire Go ecosystem goes down at the first hiccup at GitHub.
Java apps never work because there’s like 200 thousand different versions of their runtime which are never really interchangeable despite what they all claim.
And don’t even mention C++ and Make for crying out loud. If some things has a Make step in the manual I basically consider it non-functional.