Work at the Mill: The story of Digital Equipment Corporation
abortretry.fail
abortretry.fail
The pervasiveness of DEC here is amazing even after all these years. My father in law also spent almost his entire career at DEC and retired as an HP employee. One of my mentors in my late 20s (older Gen X) started his career there. I've known many other people who worked at Digital.
My only real exposure was being like 10-12 years old and getting trucked to the office during "crunch time" and I got to sit at the console on a VAX at one point and got to play early text based games on it. This was weirdly right in the machine room at the operating console as there was some rework project in the room that my father had to be present for. Later on at my first internship in the mid 1990s I had a QA job and I had to test software and I remember having to install on both Ultrix and DEC Unix and I got to use some of the Alpha machines.
There are still all these buildings and artifacts all over the place from DEC all over MA. I bank with DCU. When I was in middle school my best friend and fellow computer nerd's father worked at another Massachusetts institution.. EMC.
I never got pushed into software but it seemed to be pre-ordained... we always had computers and I was given free rein to play with them starting in the early-mid-80s but not really allowed to have video games and we always had business type machines and not the more fun consumer oriented stuff.
I VERY briefly worked for EMC after they acquired Data General which was a DEC spinoff.
This was at Portsmouth Uni in the UK. Those were all replaced with HP PA-RISC workstations after HP bought Apollo.
Apollo was founded in Chelmsford MA where I, coincidentally, bought my first house :-)
Then I later worked in the building when Cisco took over that building/park.
https://www.ricomputermuseum.org/collections-gallery/equipme...
The Retro-Computing Society of RI, a few miles away in Providence, also has a bunch of DEC stuff, also including a PDP-12. These might be the closest working PDP-12s in existence.
https://sites.google.com/a/ricomputermuseum.org/ricm-learnin...
The warehouse (Fraiser archives?) is fun, but off site from the museum. My partner noted that driving over there seemed like a start to a bad movie....
I remember the guy giving the tour telling us that he started by collecting cars, but computers seemed more manageable...
The rent those computers our for movies.
That's unfortunate. Movie people are notorious for destroying rented props. I know several (not just 1 or 2) people who rented rare to unique computers and computer parts (because who doesn't want to see your computer in a film), had them returned destroyed (painted, parts stripped off/glued on, burned or water damaged or obviously dropped from a good height), and were told 'collect the insurance...that's what it's for'. Not a single fuck given whether or not they even could be replaced.
But it must suck to have something valuable destroyed, especially if it's still functioning. I will heed this warning.
It was a while ago but I seemed to remember ber them saying the machines came back cleaner than before.
As someone who was gifted and old MicroVax (a replaced by PCs, old cad/cam machine), many of those old machines are fun to have around but aren't super useful for day to day computing. Thank goodness for emulation.
P.S.: The use of per production LLCs shut down asap to avoid all sorts of annoying 'rules' and 'regulations' is another fun topic.
I dotted lined into Tom West for a time at Data General and, later, had a >decade stint at Red Hat where I got hired on by a senior ex-DEC person.
I for one look up to people who can design, implement and debug complex systems, especially computers components and low level computer software.
In my experience many junior developers love mode switches, because they aren't sufficiently scared of complexity. "Yeah, lets add a setting to turn on or off advanced mode. Then the power users and the noobs will all be happy!".
After some time in the trenches it becomes clear to most that mode switches lead to combinatorial complexity and should be avoided at all costs.
Today we call them “feature flags”. Definitely an anti-pattern.
That said, I was once at a customer's site that had an original "blue and white" MV/8000 (the MV series in general were brown-clad). If I remember correctly what the admin said, they boot up the new 32-bit OS, AOS/VS, for part of the day, and an older 16-bit OS, either RDOS or AOS, for the rest. I wish I remembered this more clearly.
And of course the VAX-style instruction set that West's architect envied fell out of style, didn't it?
http://www.columbia.edu/cu/computinghistory/vt05.html
https://terminals-wiki.org/wiki/index.php/File:DEC_VT05_1217...
This was before my time, but I imagine that the looks said the future is now, and you're piloting a spaceship as you code.
OTOH, is love to have a 3278-2 on my desk. I’d even make an effort to make zOS into a daily driver.
I bought a rack-mount Alpha back in the early 90's running Symbolics on it. Probably all I need to say about that.
This sentence sent me down an internet rabbit hole searching for some sort of citation, as it seems absurd on the face of it. I couldn't really find an original source, but lots of comments and references about how important PDP-10s were to CompuServe. They even used clones after the platform was discontinued. It seems CompuServe kept using and updating their minis until the end.
Can you imagine maintaining a PDP-10 in the mid 2000s? Surreal. I know it's non-trivial to port software off an old computer system, but this is a machine with a clock ticking in microseconds. I can't imagine it'd take more than a week or so to reimplement any sort of business logic it had.
You're kidding right? In the old days people had to do insane things with their code to make it run fast enough. I'm thinking for example of programmers working with then-slow disk and drum storage who had to play elaborate timing tricks with their code based on when they expected data on the disk to rotate into position under the read heads. Just a few lines of assembler code, "ticking in microseconds", could conceal a terrifyingly fragile concoction of code. You could spend hours or days trying to understand it before you would dare to make a change.
Sure if you had an accurate, up to date, human-readable description of the system's "business logic" you'd be off to a flying start to migrate it to a new platform.
But the inalienable truth of old mainframe systems is that such a description no longer exists, if it ever did. The system itself - in COBOL, assembler or whatever - is the true description of the business logic. That's why IBM still sells mainframes compatible with their ancestors from over half a century ago. No-one dares to change many of these systems.
There was an epic story I once read that revolved around this and it’s going to drive me crazy until I find it.
Edit: Found it! It’s from “The Story of Mel, a Real Programmer”:
> Mel never wrote time-delay loops, either, even when the balky Flexowriter required a delay between output characters to work right. He just located instructions on the drum so each successive one was just past the read head when it was needed; the drum had to execute another complete revolution to find the next instruction.
There were also PDP-10 clones called TOAD from a company called XKL that were sold into the 80s and maybe 90s.
Both were much, much faster than the original PDP-10s.
My first job was as a *nix sysadmin for a small academic department running DECstations with ULTRIX. This was in 1993, and I helped them transition to DEC Alphas. One of the first things I did was upgrade the RAM in a 3000/500X ("hot pink flamingo". The cost of the RAM kit was more than my annual salary, so I paid extra close attention to the EST precautions.
I moved on to being research staff in a department doing OS research, and was paid to help port FreeBSD to the DEC Alpha. One of my fondest memories is getting a UP1000 from API (Alpha Processor Inc, who made Alpha boards with AMD chipsets) to port FreeBSD to. (Alpha was a bit like older Arm, and each board was a bit different w/o a generic way to discover hardware).
And to cap it all off, I got to work with Dick Sites (one of the Alpha architects) at Google. When I first met him, he autographed my old copy of the DEC Alpha Architecture Reference manual. He was the nicest guy ever, and even offered to give me a ride to the airport one day when I had a really early flight. I love it when my heros are amazing people.
Also, the linked article states:
Before enrolling in graduate school, Olsen took a summer off and traveled to Finland. His parents’ neighbor had had a Finnish girl, Eeva-Liisa Aulikki, who was a visiting student, stay with them. Olsen liked her and he failed in his initial pursuit. Yet, Olsen was a determined man. He got a job at a ball bearing factory in Goteberg.
This is just ... strangely done. The ball bearing factory was SKF's [3] in Gothenburg Sweden. Finnish girls come from Finland typically, so this part is just strange and glitchy.
[1]: https://hightechhistory.wordpress.com/2009/03/26/aulikki-ols...
Well it's a lot closer to visit Finland when you are already in Sweden than from the U.S. This was probably circa 1950 or earlier, so cheap jet travel didn't exist yet. Maybe they met up in Stockholm on weekends.
These days, I can frequently be found in said space on Wednesdays, practicing my improv skills.
Another computer mentioned was the Rainbow. DGC ported the compiler there, and in the process, wrote MicroEMACS, which is now known as MG on Linux and Unix. (Apparently this is the editor that Linus uses.)
We also had a VAX (I think it was a 730, very low-powered) to port the 8086 compiler to be hosted on VMS.
After MWC, DGC went to DEC and worked on DecTalk, an early text-to-speech device. The story goes that one member of the team, whose voice was used as the basis for the sounds, lost his voice. Thus his voice lived on only through this device.
When I was at Sycor in the late 70s, our computer was a PDP-10 (or Dec-10) running Tops 10. We wrote a cross compiler for 8085 in Bliss-36. (The assembly language for the PDP-10 was probably the most attractive I have come across.)
DGC also worked on the Alpha team (https://www.computerhistory.org/collections/catalog/X1720.99...) . He is now at Apple, and he has a side hobby of building Alpha boards out of FPGA (http://fpgaretrocomputing.org/).
When I was at Datalogics (1990-1992), who trained probably. half the world in SGML, and provided software for database publishing, legal loose leaf publishing (ask me about footnotes) and whose software was printing a substantial fraction of the red herring prospectuses at the time. They used a VAX running VMS. I had a Dec Station running some flavor of Unix. This was my first use of Emacs. As opposed to MicroEMACS.
Dr. Dennis Klatt. He developed cancer (throat of some sort, I'd assume) and did lose his voice but died within a year, AFAIK.
Perhaps more memorable than the very notable DECTalk, he built original voice synthesizer for, and was the voice of, Stephen Hawkings.
I understand Hawkings last version use a Raspberry PI, with the original voice.
I became one. My cousin followed another career.
LCM RIP.
I wish I'd managed to visit it before it shut down.
What a great place to work, and hanging out with the OS developers like Dan Murphy was just icing on the cake.
Kind of miss those days.
“Apple” (random word, even worse, it is a type of plant or something), “Facebook” (like a type of yearbook?) “Google” (sounds like they make candy or something), or “Intel” (who knows? -tel is just what companies ended their names with in the 80’s and 90’s).
DEC. What do they make? Equipment. What kind? Digital.
IBM would be good if the middle word wasn’t “business.” Business? Eh. Lame. The business is an aside, it is here to justify the machines. E, because Equipment is solid and physical.
ARM? Looks good at first. But then you find out… the A stands for Acorn. What the hell are we doing here, gardening? No. Terrible. We want D, for Digital, because we’re in the figure, the era of ones and zeros, not acorns.
AMD? Actually that name is OK as well.
something something computer science; naming things.
Anyway, they don’t sell machines. They sell designs.
and when you look at the prices of them (the setups for hotswapping) you'll go with that
Acorn is a local company for me - a load of my colleagues / contacts through the local tech scene worked there.
It's also a company whose products I originally saw in school when I was about 8 years old - they were the fancy computers, the ones kids like me weren't allowed to mess with.
We all knew RISC technology was going to change everything.
Announce your presence: RIP One.
Intel - I think tel would invoke tele like telephone or television so maybe a phone company or television studio. In an alternate world: "Get on the air with Intel - the intelligent television company!"
IBM - Incredibly Bitchin Machines
But if you really want a punchy name, something that will DEC them with the thing at the end of your ARM, well, you may as well go with a four letter acronym: FIST. I have yet to figure out what the F should stand for, but the rest is clearly Integrated Semiconductor Technologies.
That is a good point about pronouncing the name as a single word instead of three letters. Although, I still think DEC is better than ARM. Ending on the hard C adds to the oomph.
National => International
Cash => Business
Register => Machines
So each word in IBM was more generic and more widely encompassing than its correspondent in NCR.
https://en.wikipedia.org/wiki/Silicon_Graphics#/media/File:S...