permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit 03674a5e930de182645abdfd7bb252af459e89ed
parent f2c0d74e5f69430b0d3d8a0db4760df18c3d1988
Author: viznut_web <viznut_web@web>
Date:   Wed, 22 Jun 2022 15:26:02 +0200

empty web commit

Diffstat:
MUnix.mdwn | 4+---
1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/Unix.mdwn b/Unix.mdwn @@ -66,9 +66,7 @@ Disadvantages and problems their ABIs in ways that cause incompatibilities and force recompilation. * Inefficiencies and limitations that can be traced back to the pre-Unix mainframe ideals: - * Preference for sequences of plain-text lines in input and output (as - in 80-column IBM punched cards). Translating between plain-text - formats and various internal representations causes overhead. + * Preference for sequences of plain-text lines in input and output (as in 80-column IBM punched cards). Translating between plain-text formats and various internal representations causes overhead. Large plain-text files are often cumbersome to operate with. * There are good tools for defining a task (by writing a command line) but the chances to affect the running of the task are much more limited (as in the old batch-job culture). Possibilities of building