Why are large files or outputs limited?
Browser requests and shared-hosting memory are finite, so commands apply explicit bounds.
Reason
An unlimited directory walk, log read, editor buffer or network response can exhaust memory and make a shared account unresponsive.
Design
Commands limit file size, line count, recursion depth, result count, wall time or output bytes according to the operation. Errors explain which limit was reached.
Alternatives
Use filters, depth options, head/tail modes, smaller archives or direct controlled download instead of forcing an unbounded browser response.