Leo Beranek, an engineer who helped build Arpanet, has died
nytimes.com
nytimes.com
BBN was (and presumably still is, though now part of Raytheon) an amazing company to work for even 50 years after its heyday as one of the original contractors on the ARPANET project. I remember getting to meet Ray Tomlinson (who sadly passed this March) and a wide range of others who were instrumental in the early days of the internet. Seeing what was happening in CS research at the time was pivotal for me changing my career towards computer science.
One of my favorite anecdotes about the early years of the company: As mentioned in another comment, BBN started as an acoustics firm. While JCR Licklider was there briefly in the early 60s he got the company to purchase a computer. This was expensive and somewhat out of the scope of the company, when asked why purchase such the thing the response was “this company is full of smart people, they’ll figure something out”. A few years later Licklider was a PM at ARPA in charge of the ARPANET project which BBN would soon become the lead contractor on.
Leo definitely lived to a ripe old age, but he will be missed nonetheless.
https://archive.org/details/ComputerNetworks_TheHeraldsOfRes...
He was one of the fathers of architectural acoustics, noise control and vibration isolation, and remained active until the end, traveling to conferences, publishing papers and such. I met him in Seattle in 2011 at the spring Acoustical Society of America conference. Genuinely warm of a guy, always interested in others' research.
I did my master's in Acoustics (Am an M.E.), and his books were some of my go-to for "foundation" concepts in Acoustics. As a professional nowadays I still reach out to them from time to time. Like you said, he was still fairly active on conferences. He left an amazing legacy and is sure to be missed in the Acoustics community.
Very loosely, while there is lots of overlap between the three, Markoff covers the West Coast more thoroughly, with more material around his idea that a lot of the development there owes a great deal to LSD...
Levy covers the East Coast more thoroughly, going into a lot of detail about MIT, and the environment around the MIT AI Lab.
While Waldrop both goes further back, and takes a higher level view of the politics and DARPA itself.
There are of course plenty of other pieces to branch off into once you get to the rise of home computing in particular, but the above three books combine to give an even more fascinating picture of the early days of computing than they do separately. And BBN of course still stands out as one of the highly important pieces.
BBN is one of those companies that are fascinating to me, because like e.g. DEC, when I first got online in '93, they were the type of legendary that you when you are young take note of the status of, but don't really know the significance of, until you get a bit older and start being interested in the history of what you've built your career on...
'“As president, I decided to take B.B.N. into the field of man-machine systems because I felt acoustics was a limited field and no one seemed to be offering consulting services in that area,” Dr. Beranek said in a 2012 interview for this obituary.'
https://www.flickr.com/photos/jurvetson/5114191251/
Some years later, our CS department's IMP was replaced by a much smaller Cisco router (and our .ARPA e-mail addresses with .EDU addresses).
I had always associated BBN with internet engineering, so it was interesting to read that they started out in a completely different business.
[1] https://en.wikipedia.org/wiki/Interface_Message_Processor
(The IMP also functioned as a local router between the PDP-10 and the PDP-1.)
I also remember Ray Tomlinson well from the first email list on the ARPAnet, meta-appropriately about email lists, protocols, and clients.
Those were simpler times when receiving an email was done by anonymous FTP appending to your mail.txt file.
I did, it answered "Pentagon TIP," and before too long I was roving around the ARPANET. If memory serves me right the main command was "C" for connect. You simply typed "C" and a small number, and then logged in as "guest"/"guest" (the world was smaller and more innocent back then). I'm fairly certain that I logged in to a system at UC Berkeley.
"Welcome! Would you like to play a game of global thermonuclear war?"
and then you really would be worried you were connected to the Pentagon
That netted me a few laughs as friends got confused - and a summons to see the local police a few weeks later; apparently, someone had thought it WAS indeed a DoD box, reported the security breach and the next thing my local PD knew, the security services called and asked them to tell me it was quite funny and all that - but STOP DOING IT!!!
I like this guy. In a London open plan office in 2010 I measured background noise and it was above legal limits for a workplace. I mentioned it to management, nobody cared. However, I think the whole notion of 'offices should be quiet' - although valid - is now almost an anachronism.
One of my favorite memories was their warehouse of old equipment. Walking through that was like visiting a computing museum, including the only IMP I've ever seen. (Grabbed a 1GB Xyratex hard drive for an experiment; weighed 40-50lbs, IIRC. Huge.)
At the time, all of the R&D teams (the company was effectively two halves, R&D and ISP) were on a single physical network.
Roughly 2000 computers, all on a 10-base-2 network.
If you've never had the misfortune of working with 10-base-2, lucky you. I'd never seen it before, and never since. Didn't take much to bring it down.
Whenever I'd lose contact with our NFS server (NFS, sigh) I'd check my transceiver; if the yellow light was pegged, that typically meant someone in a nearby data closet had bumped the Appletalk repeater and we could count on several minutes of misery.
It seemed remarkable that the company largely responsible for building the Arpanet, who as an ISP was responsible for how many thousands of users I had no idea, had such a rickety network for its own employees.
http://laboratorium.net/archive/2013/01/12/aaron_swartz_was_...
If the whole article focused on his age, I'd be disappointed. But it's just in the headline, and the article does focus on his life.