3 ms·
Some early computers, as early as the 01940s, used binary; others used decimal, typically BCD but sometimes excess-3 BCD or one-hot encoding. Knuth's MIX was o
by kragen 5y ago
Some early computers, as early as the 01940s, used binary; others used decimal, typically BCD but sometimes excess-3 BCD or one-hot encoding. Knuth's MIX was originally specified to be either binary or decimal, as you prefer, but by the later volumes of TAOCP he switched to requiring binary for things like tries.
Typically an early (pre-01960) computer was either "scientific" or "business". A "scientific" computer was binary, had word-oriented memory of at least 16 bits width and sometimes as much as 60 or more, was measured by its calculation speed, and had floating point. (Some didn't even have separate integer arithmetic.) A "business" computer was decimal, had character-oriented memory of 6-9 bits, was measured by its I/O speed, and had only integer arithmetic, or not even that (as in the case of the IBM 1620). These categories were blurring a lot by the 01960s, and the IBM 360 largely put an end to the division: it had 8-bit-wide memory, 32-bit-wide CPU registers, floating point and binary integer and binary decimal arithmetic, and different binary-compatible models with varying degrees of speed at I/O and calculation. A few years later there were even models that supported paging and timesharing.
- kens 5y agoYes, the IBM System/360 was designed to support the full 360° circle of applications (scientific and business), which was a rather revolutionary idea at the time.
- kragen 5y agoExactly! But in terms of design, there were earlier machines that spanned the gap like the astounding Burroughs B5000, which was marketed almost entirely to businesses (because that was the Burroughs customer base), but with a 48-bit word length and floating-point-only arithmetic, and including both "numerical" and "character" instruction set operating modes. The first delivery was, I think, to NASA. Also, as Robert points out in https://news.ycombinator.com/item?id=30900280 https://news.ycombinator.com/item?id=30900280, the earlier IBM 1620 was similarly ambiguously positioned.
- Taniwha 5y agoTo be fair the B5/6/7 Burroughs machines also had integers ... it's just that they'd chosen a floating point format such that mantissa-sized integers and a 0 exponent always worked and didn't get renormalised unless you overflowed
- kragen 5y agoInteresting! That does agree with Organick's explanation, but he described it as them not having integers.
- tenken 5y agoWhy do you reference a year via 01960 or 01940? ... Surely you don't mean Hexadecimal... You won't live past 20x0 so why the importance?
- krallja 5y agoY10K compliance. https://longnow.org/ideas/02013/12/31/long-now-years-five-digit-dates-and-10k-compliance-at-home/ https://longnow.org/ideas/02013/12/31/long-now-years-five-di...
- gugagore 5y agoTo me, "compliance" suggests that adherence prevents an issue, but there is no ambiguity in writing a 4-digit year. I currently have a computer with 16 GiB of RAM. But to be future-compliant, I should write it out as 016 GiB? I appreciate the explanation, in any case.
- alar44 5y ago
- rst 5y agoThe 1620 was an odd duck: variable-word-length decimal, as you point out, but targeted at the scientific market -- there was even a variant, sold as the 1710, which added extra hardware for industrial controls. (The 1401 and its successors were the nearly-contemporary low-end business models; there are a bunch of differences, but perhaps the most significant is that a single 1401 memory location could hold a decimal or alphabetic character; the 1620's memory locations were digits, which had to be paired when representing characters, making coding for anything involving character data a whole lot more awkward.)
- kragen 5y agoOh my. I had no idea. Thank you.