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.
Data visualization ≠ UI and signal processing is traditionally done in C
That looks like buttons in the thumbnail, on the left of the visualisation.
I’d say that’s enough to call it UI.
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?
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.
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.
Would you agree that the dashboard of a car is UI? If so, isn’t that just data visualization?
Dashboard is a UI fed by signal processing code which is the backend.