Bell Labs Unix Group Disbanded
wandazulu writes "Peter Salus over at UnixReview.com is reporting that AT&T Department 1127, responsible for creating and maintaining Unix, has been officially disbanded. The article provides an interesting "where are they now?" list of the original authors of Unix."
I think this is sad, and a little ominous. I worked at a telco years ago, and managed to fanagle a chat on the phone with Ritchie one time when a Bell worker was on site for some software installations. Cool.
Anyway, in my arguments to encourage research into trying new ways of doing things, I always used Bell Labs as my favorite example/reason why we should. Guess I won't have that anymore. Sigh.
What I fear most is the lack of research for research's sake. A lot of things we use today are a direct or indirect result of companies allowing a certain amount of "what if" thinking and activity to go on. Even better, some companies, like Bell Labs actually allocated specifically for that.
I don't think research in commercial context is really research at all and may even be counterproductive in creating new and better technology (if commercial research into products were for "quality", would there even be a Britney Spears?).
The last bastion I know of and trust is Google. They seem to be dedicated to the cause. But, they're young, they're new, and they haven't had to deal with stockholders in bad times yet.
I worked at Bell Labs in Murray Hill from 1985 through 1989, and though I did not work in Dept 1127, I did get the amazing chance to see what Bell Labs was all about: the incredible, vibrant home to tremendously talented scientists from the UNIX gurus to the low temperature physics gods. As a young high school and then college student, aspiring to join their ranks full time, I was mesmerized by the environment where a 2pm coffee break could evolve into a deep discussion of networking theory and then reflect sincerely on the goings-on in the world. Bell Labs was a magical place, and hopefully, the seeds of similar pure research incubators are being sewn in today's tech powerhouses such as Google.
I had the good fortune of meeting the gentleman when I interviewed with Mathworks a couple of years ago. I was taken aback by his humility, and the poor guy was embarrassed when I requested his autograph :) He has a former license plate in his office that reads "YACCMAN".
An Indian-American Hindu committed to non-violent thought/speech/action alarmed by the global explosion of radical Islam
If Bell can fall, then this event only proves that Google will someday fall. It is all just a great progression of humanity. And hopefully before that fall a little more technology will come to push mankind farther. Good job Department 1127!
I mean, there's something to be said for learning data structures and operating systems from a guy who helped invent the idea of pipes.
McIlroy's homepage.
Although IBM http://www.research.ibm.com/ may be out of the disk drive business, they are still working on it. Take a look at the Almaden Research Center in San Jose http://www.almaden.ibm.com/ still going strong after all these years.
It seems like they would have a hard time attracting the talent to keep the group open. My dad, an 18 year Bell Labs veteran, left Telcordia /Bellcore/Bell Labs five years ago. The downturn in the tech industry forced many others to leave for more lucrative jobs while they were still available. Two of the math/CS teachers at my old high school were from Bell, for instance.
A few things come to mind
1) Making the command interpreter a user level process instead of an integral part of the kernel.
2) Treating all files as simple streams of data. Mainframes of the day that I've had experience with all forced some type of record format on files.
3) Making everything visible to the sytem as a file(file systems, devices, message queues). On other systems these are handled via special reserved words understood by the command interpreter or system.
4) Pipes between processes.
5) The C programming language itself.
Much of this seems like common sense today, but they were new ideas around 1970. Some of them were probably taken from other research operating sytems of the time and reimplemented as software patents were'nt the problem they are today.
"A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis
You see, to me, mindless applications of fourier transforms and other mathematical techniques describes engineering, whereas coming up with new ideas and algorithms describes research.