4 ms·
How to tell a mainframe from a minicomputer from a micro
- rahen 4y agoOriginally a HN reply posted here: https://news.ycombinator.com/item?id=32969692 https://news.ycombinator.com/item?id=32969692
- lproven 4y agoExactly -- that's why I didn't post it. I write for a living so seldom have time to do it for my blog as well -- so I take longer comments from here and other places, trim them and post 'em on the blog. Keeps it from falling silent.
- lproven 4y agoOh -- thanks! It is just a repurposed HN reply, which is why I did not post it myself.
- ncmncm 4y agoSo now microcomputers are mainframes, but with all that extra hardware virtualized and emulated.
- projektfu 4y agoYeah, sort of, but it's more like this: First, there were computers. There were some that were made to be small enough for a group (IBM 1620, for example), and some that were large and intended as the central device for a large organization (IBM 7090). IBM referred to both as a "data processing system". These were delivered as batch-oriented systems. Large computers like the 7090 often had smaller, accessory, general-purpose computers that handled things like card reading/punch and printing. For example, the PDP-10 had a PDP-11 as its front-end controller. In the late 60s the term minicomputer appeared. A little while later, it became popular to refer to the large computers as "mainframe" computers. This probably was marketing speak to imply that, while minicomputers can be good for somethings, you wouldn't mini-frame your house, so you had better main-frame your company. I like to think about this time, which was also the heyday of database innovation, as the time when companies thought there would be many integrated applications running on the same data base [two words at the time] operated by a large, reliable computer and accessed by peripheral terminals. Through the 80s, people in companies often referred to "the computer" rather than considering multiple computers as the norm. Microcomputers appeared with the development of the microprocessor. Certainly, the Altair 8800 started the wave of using a fully integrated microprocessor as the basis for a general-purpose computer. They grew out of calculators and, tellingly, from the project to develop an intelligent display terminal. Micros often looked like minis in their use - they might be operated by terminals and punched tape, saving onto hard disks, floppy disks and magnetic tape. In my opinion, the distinction was if you used a discrete ALU, like the VAXes or the Xerox Alto, you were still using a minicomputer. Many minicomputers used ECL* to achieve high speeds that were not reachable by NMOS or CMOS logic at the time. Eventually, minicomputers also became microcomputers, for example, the MicroVAX. I think that these articles get it right that the microcomputers are different because they are not considered to be the orchestrator of a system of disks, tapes, terminals, printers, etc. They are at best part of a network with specialized microcomputers helping share resources when needed. There is trend of data ending up in silos that happens with minicomputers and microcomputers. Applications get written for their own data, they aren't given direct access to other applications' data, and the data itself is geographically distributed. As time has gone on, we now have the datacenter and virtualization. Data has been moving out of silos and into large, shared databanks. The computing unit is no longer made out of hardware, but rather represented by resources that can be provided in many virtualized ways. * Emitter-coupled logic, a high-speed discrete logic often used in supercomputers and fast general-purpose computers until CMOS caught up with better power and heat characteristics.
- ghaff 4y agoAt the end of the day, a lot of the classifications are at least somewhat historical. And somewhat dependent on what operating systems they ran as well in addition to morphing in various ways over time. (At some level most modern servers are micros unless you're going to create a new category for them as you wouldn't usually refer to them that way.) You also have "Big Iron" Unix servers in there somewhere. And various specialty scientific computing systems, e.g. all the vector supercomputers etc.
- projektfu 4y agoYup, the categories are very fluid now. Considering how many businesses "run" on some various software packages these days, they all have some sort of mainframe, but it's not likely to be one computer. I think, only the minicomputer is really gone. There just isn't the same sort of way of using the computer that there was in that time.
- masswerk 4y agoI'd make a point that the entire line of experimental computers as developed at MIT and later commercialized by DEC, with an emphasis on realtime and graphics, doesn't really adhere to this pattern. E.g., we may call the PDP-1 the first commercial workstation. (Single user, realtime, graphics, used for exploratory work, emphasis on I/O capabilities with a large array of input and output devices. But the PDP-1 saw also use as a small mainframe and was a testbed for time sharing.) In a sense, minis began conceptually as downgraded workstations. (Which became viable only as memory cycles shrunk, thus allowing for smaller word sizes.)
- psim1 4y agoI worked at a company in the early 1990s that ran its business on an IBM System/36. It was basically a System/360 but one tenth of the size and expense! This was the only minicomputer I ever encountered, and I was not responsible for it. I was there to work on the "micros" (Windows PCs). I remember the System/36 programmer making comments about PC techs not being "real" computer operators or programmers. She was nearing retirement at that time, and if she is still alive I imagine she is enjoying a comfortable pension.
- klelatti 4y agoMy first job in 1984 included 'selling' System/36s - I say 'selling' in inverted commas as I don't think we actually sold a single machine - the other part was selling PC/XTs which was much easier. Also customers weren't that keen. By 1990 it would have been a desktop S/36 which sat on or under your desktop. The first version was the shape of a washing machine but about 6x bigger by volume. It was also incredibly slow. I later came across an insurance company that ran its business on a S/36 emulated on a 386. The emulation was faster than the original machine. From memory I don't think the architecture had much in common with S/360. Quite simple I think but a lot of the internal state of the processor exposed to the programmer. Might do a blog post on it at some point! Edit; Do let me know if a blog / newsletter post would be of interest - details in my bio. Thanks!
- ThinkBeat 4y agoDo you remember the name of the emulator? Was it provided by IBM, if so was not running production on it against the TOS? If it was not supplied by IBM then it was certainly not legal as far as IBMs legal team is concerned. I only ever saw a demo of the IBM emulator. It was only offered for short time if memory serves. I do remember the emulator being painfully slow. This is not strange given the amount of emulation it had to do to emulate the SYSTEM/36/360 architecture. The IBM model 5364 was called the "System/36 PC" or "Desktop 36"is about the size of a regular computer. The full machine fits your description well https://www.wikiwand.com/en/IBM_System/36 https://www.wikiwand.com/en/IBM_System/36 https://www.recycledgoods.com/ibm-5364-s-36-pc/ https://www.recycledgoods.com/ibm-5364-s-36-pc/ https://www.youtube.com/watch?v=Y9oa5g5FWss https://www.youtube.com/watch?v=Y9oa5g5FWss
- matja 4y agoIf there is someone phoning you or knocking on your door when you turn it off, it's not a microcomputer.
- baybal2 4y ago
- otabdeveloper4 4y ago> Separate processors in storage, in terminals, in networking controllers, in printers, in everything. Typically the machine cannot actually drive any output or input directly (e.g. mouse movements, or keystrokes, or anything): peripherals do that, collect and encode the results, and send them over a network. Sounds exactly like USB.
- rvense 4y agoUSB? You mean that thing that all the 8051s use to talk to each other?
- zerohp 4y ago> So as someone else commented, a mainframe isn't really a computer, it's a whole cluster of closely-coupled computers, many with dedicated functionality. Quite possibly all implemented with different architectures, instruction sets, programming languages, bit widths, everything. Nearly all computers more powerful than a simple microcontroller look like this in 2022. If you find this fact surprising, you'll probably want to take a look at this talk from USENIX ATC '21: https://www.youtube.com/watch?v=36myc8wQhLo https://www.youtube.com/watch?v=36myc8wQhLo
- GMoromisato 4y ago> a mainframe isn't really a computer, it's a whole cluster of closely-coupled computers, many with dedicated functionality. This is a great description. I think we're moving back to the mainframe architecture, but the "cluster" now includes all the machines in a data center, plus the mobile and PC clients connecting to services. Tangentially: I talk about how programming models have evolved from the mainframe to today here: https://gridwhale.medium.com/gridwhale-and-a-brief-history-of-computing-be24e5263328 https://gridwhale.medium.com/gridwhale-and-a-brief-history-o...
- rhn_mk1 4y agoConsidering how many programmable computers with dedicated functionality a typical laptop contains, I think they are already clusters. Except those are typically not possible to program by the user, with a few notable exceptions: some older WiFi cards, a few Embedded Controllers. Forget about reprogramming the hard drive.
- mrjin 4y agoYep, I was about to reply with similar stuff but yours posted first. So it's the case when PC came out, but now as you said, modern PCs are already clusters of computers with dedicated functions. The main differences between PC and Mainframe are around: 1. CPU instruction set. 2. Provisions for high availability/reliability and IO at scale.
- rbanffy 4y ago> Forget about reprogramming the hard drive. The idea of embedding compute into memory so that a number of small processing units could sit directly on the very wide paths to the memory is not new, but has surfaced a few times lately. If a memory copy or move can be issued by the CPU and never cross the DDR5 path, it’d be a huge win. I don’t see slow peripherals such as hard drives having the same need, but flash memory devices could be more interesting. Some 8-bit computers such as the Ataris and, to a lesser degree, the Commodores, has intelligent peripherals. Atari had a serial bus where you’d daisy chain storage, modems, printers, etc, each with its own little computer and OS. On both, IIRC, the storage device was responsible for the file system while the computer communicated file operations (open, read, seek) over the wire and got results back. It’d, in theory, be possible to send small programs to do specific actions (defrag the disk, filter a text file) without tying up the computer.
- manv1 4y agomainframe: building sized minicomputer: room sized microcomputer: desk sized
- mrjin 4y agono longer the case