What does buffered input mean in practice?

A buffer is a temporary area of memory between your program and the operating system. Communicating with the OS for every individual character is relatively expensive, so input is collected into a chunk—often a whole line—and then delivered to your program together. Instead of handling “H”, “e”, “l”, “l”, and “o” as separate OS operations, the system can provide the entire string at once.

For terminal input, buffering commonly means your program does not see each keypress immediately. The system collects what you type and makes it available when you finish the line and press Enter. Character-by-character input is possible, but it usually requires a special unbuffered mode so the program can receive keys, tabs, and control sequences as they happen.

More generally, a buffer is a queue of memory that lets two parts of a system work at different speeds. The sender can place incoming data in the queue while your program processes older data. This helps prevent delays or lost data when one side is temporarily busy, and it also improves performance by favoring fewer, larger read operations instead of many tiny ones.

Buffers are also useful when reading files or streams. Rather than loading an entire potentially huge file into memory, the program reads a manageable block, processes it, and then replaces it with the next block. Buffered input therefore improves both memory usage and efficiency. The tradeoff is that the data your code reads may have arrived earlier and be waiting in the buffer, rather than representing the source at that exact instant.