No! high level languages should not be used to write systems software

ABSTRACT

The views expressed here derive from the experience of the author and his colleagues in designing and implementing the Octopus computer network at the Lawrence Livermore Laboratory. This network serves five major time-shared computers (CDC 7600's and STAR-100's), connecting them to over 800 interactive terminals, about 200 television monitor displays, printers that operate at up to 18,000 lines/minute, and more than a trillion bits of storage. The software for the network has been written entirely in assembly language (for PDP-8's, 10's, and 11's, MODCOMP II's, and TI 980's) and from scratch, basing none of it on manufacturers' or other commercial software. The same persons who create the design also do the programming and debugging. In most cases one or two persons program a computer; four persons were used on the largest system (the PDP-10's). Our experience does not accord with much of what we read in the computing literature, leading us to conclude that it is written by persons unaware the real problems of systems work. We have had little or no trouble with deadlocks, security loopholes, and other logical flaws that are belabored at length in the literature. Most of our effort has gone into devising ways for the system to survive in the presence of intermittent and random failures of hardware components and for it to maintain high data transfer rates among multiply-interconnected devices and computers of varying speeds, matters that are seldom discussed in the literature at all. It is certainly not the case that the difficulties encountered with operating systems are the same as those encountered with other large programs, such as compilers.

REFERENCES

• 1: Beale, E. M. L., Fortran Programming Conventions, Scientific Control Systems Ltd., London, W.l.
• 2: Frederick P. Brooks, Jr., The Mythical Man-Month: Essays on Softw, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1978
• 3: B. L. Clark , J. J. Horning, Reflections on a language designed to write an operating system, ACM SIGPLAN Notices, v.8 n.9, p.52-56, September 1973
• 4: Conway, R. and D. Gries, An Introduction to Programming (2nd Ed.), Winthrop Publishing, Inc., Cambridge, Mass., 1975.
• 5: Donahue, J. and E. Lazowska, eds., Proceedings of a Scientific Symposium on Software Engineering Education, IBM Canada, Montebello, Quebec, May 5-7, 1975.
• 6: DX980 General Purpose Operating System Programmer's Guide, Texas Instruments Incorporated, Digital Systems Division, Part No. 943005-9701.
• 7: Fletcher, J. G., "The Octopus Computer Network," Datamation (19:4), April 1973, pp. 58-63.
• 8: J. G. Fletcher , C. S. Badger , G. L. Boer , G. G. Marshall, On the appropriate language for system programming, ACM SIGPLAN Notices, v.7 n.7, p.28-30, July 1972 [doi>10.1145/953360.953361]
• 9: J. D. Gannon , J. J. Horning, The impact of language design on the production of reliable software, Proceedings of the international conference on Reliable software, p.10-22, April 21-23, 1975, Los Angeles, California
• 10: Greenberg, H. J. and J. E. Kalan, "Some Tactics for 0-1 Programming," ACM SIGMAP Newsletter, No. 15, 1973, pp. 30-34.
• 11: Per Brinch Hansen, Operating System Principles, Prentice Hall PTR, Upper Saddle River, NJ, 1973
• 12: Hoare, C. A. R., "Hints on Programming Language Design," Proceedings of ACM SIGPLAN/SIGACT Symposium on Theory of Programming Languages, Boston, October 1973.
• 13: Hopkins, M., "The Programmer as Hero," private communication, 1971.
• 14: Hopkins, M., "SABRE PL/I," Datamation (14:12), December 1968.
• 15: Donald E. Knuth, The art of computer programming, volume 1 (3rd ed.): fundamental algorithms, Addison Wesley Longman Publishing Co., Inc., Redwood City, CA, 1997
• 16: McKeeman, W. M., "On Preventing Programming Languages from Interfering with Programming," IEEE Transactions on Software Engineering (1:1), March 1975, pp. 19-25.
• 17: Orchard-Hays, W., Advanced Linear Programming Computer Techniques, McGraw-Hill, 1968.
• 18: PL/I(F) Language Reference Manual, No. GC28-8201-4, IBM Corporation, White Plains, N.Y.
• 19: "Proceedings of a SIGPLAN Symposium on Languages for Systems Implementation," SIGPLAN Notices (6:9), October 1971.
• 20: Requa, J. E., "In-House vs. Vendor-Supplied Software: A Case Study at the Lawrence Livermore Laboratory," Atomic Energy Systems, Operations, and Programming Meeting, October 1972.
• 21: Paul Gordon Sorenson, A methodology for real-time system development., 1974
• 22: Nobuyoshi Terashima, SYSL: system description language, ACM SIGPLAN Notices, v.9 n.12, p.35-44, December 1974 [doi>10.1145/953246.953250]
• 23: van der Poel, W. L., Machine-Oriented Higher-Level Languages, Proceedings of an IFIP Working Conference, North-Holland, 1974.
• 24: Weinwurm, G., On the Management of Computer Programming, G. Weinwurm, Editor, Auerbach Publishers, Inc., 1970.
• 25: Wirth, N., "On the Design of Programming Languages," Information Processing '74, IFIP Congress, Stockholm.
• 26: William Allan Wulf , Richard K. Johnsson , Charles B. Weinstock , Steven O. Hobbs , Charles M. Geschke, The Design of an Optimizing Compiler, Elsevier Science Inc., New York, NY, 1975

INDEX TERMS

Primary Classification:
  D. Software
  D.3 PROGRAMMING LANGUAGES
      D.3.2 Language Classifications
          Subjects: Very high-level languages

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

General Terms:
Languages