I just realized that when you write C/C++ code or the like, it just keeps the code and data stored in object files for execution, but doesn't do anything.
A linked library will need to access a low-level driver, link objects together and library files, all to finalize one image with all of the code and data requests.
So technically, your C code alone is garbage. You are writing code that needs to be linked with other code to get a full working image with sound and video access, etc.
Kind of a buzz kill, right? Window/Mac/Linux drivers are doing the big work.
So technically, your C code alone is garbage. You are writing code that needs to be linked with other code to get a full working image with sound and video access, etc.
By this reasoning, drivers are also garbage unless there's a program to use them. Both of these cases are true, but the use of the word "garbage" to describe either process is inappropriate.
By this logic, anything that input that is provided to a server, in the history of the universe, has been completely useless. Python scripts? Useless. Init scripts? Garbage. Assembly? Forget about it. It was the assembler that did the real work.
Real programmers code directly in machine code, create the executable headers themselves, and manually copy and pastes the machine code together using machine code as well.