3 ms·
I think the make example was more aimed at the sprawling number of specialized "downloaders". Starting with erl cpan and moving on to ruby gems and similar. It
by digi_owl 12y ago
I think the make example was more aimed at the sprawling number of specialized "downloaders". Starting with erl cpan and moving on to ruby gems and similar.
It was not so much that there is a unified command, but that you could reasonably expect that either it was self contained, or the dependencies were spelled out somewhere. Now it is "let cpan/gems/whatever grab all the magic pixie dust while you get coffee".
Sure works fine for a lone dev at their desktop, but in a production environment handling perhaps millions of users and dealing with a mass of regulations?