UI. User Interface. The bridge between a system and a user. So anything, literally any information transfer from the user to the system OR from the system to the user, is a User Interface.
I did not make this definition. However, this does not give you the freedom to make up your own definition and treat it as a fact. Don’t spread wrong information.
why would you take the least charitable interpretation? there is no need to be hostile.
and the answer, of course, is that it can be, as long as the information copied is meaningful for displaying to the user.
you’re basically asking the equivalent of whether putting things into an array is an algorithm, which of course has the answer “it can be, depending on how you put it in”. so basically, the operation you’re highlighting is not the point.
UI. User Interface. The bridge between a system and a user. So anything, literally any information transfer from the user to the system OR from the system to the user, is a User Interface.
A definition so broad as to be useless.
Is it a UI when someone calls memcpy to move data from a file to a screen buffer?
Not it isn’t.
A command line literally is a UI.
You seem to be confusing GUI and UI?
You seem to be confusing C stdlib with a CLI?
I did not make this definition. However, this does not give you the freedom to make up your own definition and treat it as a fact. Don’t spread wrong information.
This isn’t hard, you’re just trying to make it to be.
Memcpy from a file to a screen buffer is as much a UI as pouring water in a pot is a soup.
why would you take the least charitable interpretation? there is no need to be hostile.
and the answer, of course, is that it can be, as long as the information copied is meaningful for displaying to the user.
you’re basically asking the equivalent of whether putting things into an array is an algorithm, which of course has the answer “it can be, depending on how you put it in”. so basically, the operation you’re highlighting is not the point.