4 ms·

The C programming language predates the time when using third party libraries was common. When it became commonplace to depend on third party or system librari

by qsort 5y ago

The C programming language predates the time when using third party libraries was common. When it became commonplace to depend on third party or system libraries, because of the special status C enjoys in the software infrastructure, OS and distro developers bend over backwards to accomodate C linkage, providing pre-packaged dynamic linking objects. The status quo is actually rather unfortunate. Several package management tools exist to attempt to address the issue, but there is no de-facto standard and every project makes its own choice.

dotancohen 5y ago
> The C programming language predates the time when using third party libraries was common. The English language predates spaceflight, but has adapted. PHP predates proper security practices, but has adapted. Javascript predates the Document Object Model but has adapted. For that matter, Javascript also predates the time when using third party libraries was common.
- qsort 5y ago
  I'm not passing a value judgement, that was simply an "historical" account of what happened. C had such a powerful influence on computing that it didn't need to adapt to the world, the world adapted to C.
- II2II 5y ago
  Yet language still takes time to adapt. Formally, it takes years for words to enter the dictionary. Informally, it takes time for new vocabulary to spread. For example, in the early days of computers, it was very common for terminology to be used incorrectly. Of course, there is more going on with C than the use of new "words" introduced through libraries. Even though it is viewed as a portable language, most of that portability is between hardware architectures and operating systems of the same class. Almost everything above that is handled by vendor specific libraries so there was likely less of a drive to standardize on library management. This has negative consequences in today's environment, but it would have taken foresight to predict that outcome.
- nephanth 5y ago
  The english language doesn't really maintain retrocompatibility though
- tomc1985 5y ago
  Be the change you want to see, then?
  - dotancohen 5y ago
    You're not the first to suggest that I need better package management... what has my ex been telling ?!?

by qsort 5y ago

dotancohen 5y ago

> The C programming language predates the time when using third party libraries was common. The English language predates spaceflight, but has adapted. PHP predates proper security practices, but has adapted. Javascript predates the Document Object Model but has adapted. For that matter, Javascript also predates the time when using third party libraries was common.

qsort 5y ago
I'm not passing a value judgement, that was simply an "historical" account of what happened. C had such a powerful influence on computing that it didn't need to adapt to the world, the world adapted to C.
II2II 5y ago
Yet language still takes time to adapt. Formally, it takes years for words to enter the dictionary. Informally, it takes time for new vocabulary to spread. For example, in the early days of computers, it was very common for terminology to be used incorrectly. Of course, there is more going on with C than the use of new "words" introduced through libraries. Even though it is viewed as a portable language, most of that portability is between hardware architectures and operating systems of the same class. Almost everything above that is handled by vendor specific libraries so there was likely less of a drive to standardize on library management. This has negative consequences in today's environment, but it would have taken foresight to predict that outcome.
nephanth 5y ago
The english language doesn't really maintain retrocompatibility though
tomc1985 5y ago
Be the change you want to see, then?
- dotancohen 5y ago
  You're not the first to suggest that I need better package management... what has my ex been telling ?!?