Unix and Google

Channel:FOAM · Length:7:15 · Published:2016-02-05 · Views:9321

Watch on YouTube

Summary

A short animated simulation comparing how Multics and Unix were developed, showing why Unix's small composable programs and pipes gave it a efficiency advantage. It frames Unix as a moonshot achievable by a small team.

Why HN recommends it

Cited constantly in threads on microservices, composability and the Unix philosophy as a compact explanation of why small interoperable pieces win.

A guy on YT [1] simulates in 7 minutes how the two biggest operating systems were built in the sixties — HN, 2021

Software architecture & design · Operating systems & kernels · History of computing

Subtitles (excerpt)

my name is Kevin gur and I lead the foam team at Google I'd like to give a little history lesson so the second largest engineering project of the 60s um was IBM system 360 the largest of course was putting a man on the moon so it was thought that uh really creating a new operating system was like a mammoth um you know engineering undertaking so really to compete with that um they created an operating system called multics and this really combined the required the combined forces of MIT AT&T which was the largest Communication company at the time and General Electric which was the largest company of any type at the time so these three companies uh combined to create this new operating system called multics and so what we're showing in this diagram is the little blue dots represent the multics developers and they're running around and they're going to write code which is code is in green and this Square represents the operating system so along this axis we have the different types of data an operating system we need users groups processes devices Etc and then across the top we have the features um that each of those that you would need for each of that type of data sorting search paging

On Hacker News

I wrote a non-programmer summary to some of my friends, because my mind is blown. Here it is (warning: it's very informal). This is some next level 80/20 stuff, I'd argue it's even 99/1 (consultant speech for "being efficient" by seeing if you can exploit Pareto's principle [0]). A guy on YT [1] simulates in 7 minutes how the two biggest operating systems were built in the sixties (Multics by IBM… — mettamage, 2021-06
I was going to comment on this very thing in the other thread about software glue[1]. In that article there is a youtube video on Multics vs Unix[2] which really outlines why microservices were always doomed. Someone should coin a new law for how programmers have to rediscover Brooks's law every 5-10 years. The issue with microservices, as it has always been, is that you need an enormous company … — deckard1, 2021-06
Unlike previous OSes, UNIX provided the pipe facility to allow you to combine the functionality of many small programs. Ex. ls | grep ... | sort ... | more Before that every command-line program had to support the full suite of additional functionality like search, filtering, paging, etc. This UNIX/Pipe approach allowed for greater reuse and much less code. This is explained and simulated in this… — kgr, 2023-09
If we analyze the computational complexity of software architectures the way we do regular algorithms, we see that UNIX was much more efficient than previous OSes/approaches. It's demonstrated in this short video: [VIDEO] — kgr, 2023-08
Programs/functions like left-pad do not follow the unix philosophy (which the author did say). The idea of the unix philosophy is to write less programs. Not write a ton of tiny programs, but a small number of composable programs. So instead of left-pad, right-pad, middle-pad, and anything else to get specific need you can use sprintf which can format a string in general, one program that can do … — foooobaba, 2022-11

Related videos