←back to thread

416 points henry_flower | 2 comments | | HN request time: 0.479s | source
Show context
m4r1k ◴[] No.43112034[source]
I once saw a talk from Brian Kernighan who made a joke about how in three weeks Ken Thompson wrote a text editor, the B compiler, and the skeleton for managing input/output files, which turned out to be UNIX. The joke was that nowadays we're a bit less efficient :-D
replies(7): >>43112150 #>>43112344 #>>43112772 #>>43114120 #>>43117365 #>>43118374 #>>43118624 #
Cthulhu_ ◴[] No.43112772[source]
A newer joke is that Ken Thompson (along with Rob Pike and Robert Griesemer) designed Go while waiting for C / C++ to compile.
replies(2): >>43116523 #>>43126057 #
kragen ◴[] No.43126057[source]
Not C/C++. Specifically C++. C compiles pretty fast. And it's not really a joke, though obviously it wasn't a single build they were waiting for.
replies(1): >>43133710 #
pjmlp ◴[] No.43133710[source]
Back in 2000, our builds, C modules to be consumed by Tcl, Apache and IIS modules, DB drivers took about one hour per OS for a full platform release.

OS being Windows NT/2000, Aix, HP-UX, Solaris, Red-Hat Linux.

replies(1): >>43134395 #
kragen ◴[] No.43134395[source]
Yeah, that's similar to my experience. C++ projects commonly took a week to build in the 90s.
replies(1): >>43136737 #
1. pjmlp ◴[] No.43136737[source]
I can assure that wasn't the case in our desktop software for Windows, and that already feels like trolling.

Not even Nokia NetAct took half as much, given its complexity of distributed CORBA services written in C++, nor the CERN TDAQ/HLT builds I was responsible for.

replies(1): >>43137911 #
2. kragen ◴[] No.43137911[source]
You were probably working on more competently designed software than I was, but sure, desktop software for Windows usually didn't take that long.