A consistent coherent complete vision of the system

[sujonkumar6300]

That recommendation, it seems to me, is a good mitigation — but it doesn't prevent or cure the problem. My recommendation is a couple of steps away from the instant gratification provided by language-specific package managers (npm for Node/Javascript, Gems for Ruby, Pip for Python, etc.).

Personally, I draw my practice from the culture of Linux distributions, particularly Debian. For several years I have been advocating the advantages of the system-level packaging philosophy: While it makes sense for a developer to have the latest versions of the libraries he uses and to know the details of how they work, the same cannot be expected of the end users of a tool.

If I'm installing a particular package to manage my Bitcoin wallet (or anything else), I shouldn't even care what language it's written in, let alone whether I'm going to install it using one or another packaging framework. Most users sri lanka email list are interested in solving their problem from a single software management interface. Granted, in the case of Node, many of its applications are intended to be installed centrally, on a server, by a system administrator, not an end user. Still — if that administrator is expected to employ the development (as opposed to using it as a basis for further development), why force him to learn yet another idiosyncrasy, yet another way of managing a tiny bit of the system?