frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Open in hackernews

Powering up a module from the IBM 604: an electronic calculator from 1948

https://www.righto.com/2026/06/ibm-604-thyraton-tube-module.html
34•elpocko•1h ago

Comments

kens•1h ago
Author here for your vacuum tube questions...
Retro_Dev•36m ago
No questions, but I really enjoyed the article - thank you for sharing. It amazes me how few vacuum tubes these early computers use, compared to the billions and trillions of mosfet transistors used in modern devices.
kens•18m ago
One way they get away with using relatively few tubes is that most of the Boolean logic is done with semiconductor (germanium) diodes, using tubes to amplify the results.
Animats•4m ago
That's a machine from IBM's 600 line, cost-effective business machines that did automated arithmetic. The IBM 601 (1931) read and punched punch cards, multiplying fields as set by a plugboard. It was entirely mechanical. The IBM 602 (1946) was similar, and could divide. The IBM 602A ("a 602 that worked" 1948) was in wide use into the early 1970s.

IBM had been working on electronic arithmetic prior to WWII, and the IBM 603 Electronic Multiplier (1946) was IBM's first deployed product with large numbers of tubes. It was built to find out if tube machines could be successfully deployed in a business environment and used commercially without constant tending by skilled technicians. That was the commercial limitation - the ENIAC and UNIVAC sized machines required large numbers of on-site techs to keep the hardware going. The 603 didn't. All IBM machines at the time were rented by IBM, and rental included on-site servicing by IBM Customer Engineers in white shirts and ties. IBM had to keep the servicing cost down. IBM was only willing to deploy tubes if the operating and maintenance costs were acceptable.

The 604 was a more commercial version of the 603. The 603 looked like a very large suitcase built of black perforated metal. The 604 looked like IBM's other tabulating machines and had better access to the components. This was the first high-volume product with tubes.

None of these machines had much memory. Just a few registers. There were no good memory devices yet suitable for field deployment. They were all programmed with plugboards. Everybody involved knew they needed better programmability, and there was an effort at Columbia University in the 1930s to do that. It involved Eckert and Mauchley, who went on to design the ENIAC and the UNIVAC I. But there was no good place to put the program.

The memory problem persisted for years. Williams tubes were unreliable. Acoustic delay lines had temperature stability problems. Rotating drums could work at a commercial price point. The IBM 650 (1953) was IBM's first real business computer, with drum main memory and all-electronic computation. Knuth's first book is dedicated to the IBM 650.

This side of computing gets less attention in histories, which tend to focus on the military machines. But this was the side that shipped in volume and made real money. It's came from the engineers with relays and clutches in Endicott and the accountants at Armonk, who had to develop something IBM Sales could sell to large and medium sized businesses. No need for Turing, von Neumann, etc.

The IBM 1401 (1959) ended the 600 line. At last, all-transistor, all core memory, in a reliable box that could be deployed to customer sites. It's a very strange machine, with variable-length everything, but it works well. Then, of course came the IBM System/360, which standardized architecture for decades to come.

Powering up a module from the IBM 604: an electronic calculator from 1948

https://www.righto.com/2026/06/ibm-604-thyraton-tube-module.html
35•elpocko•1h ago•5 comments

Leiden Declaration on Artificial Intelligence and Mathematics

https://www.lms.ac.uk/news/leiden-declaration-on-ai-and-mathematics
12•_____k•32m ago•1 comments

Cloning a Sennheiser BA2015 battery pack

https://blog.brixit.nl/cloning-a-sennheiser-ba2015-accu-pack/
66•zdw•1d ago•13 comments

Silurus/ooxml: Pixel-faithful Office documents, rendered in the browser

https://github.com/yukiyokotani/office-open-xml-viewer
18•maxloh•1h ago•8 comments

What is the purpose of the lost+found folder in Linux and Unix? (2014)

https://unix.stackexchange.com/questions/18154/what-is-the-purpose-of-the-lostfound-folder-in-lin...
35•tosh•2d ago•19 comments

The 29th International Obfuscated C Code Contest (IOCCC) 2025 Winners

https://www.ioccc.org/2025/
324•matt_d•13h ago•76 comments

Show HN: Lathe – Use LLMs to learn a new domain, not skip past it

https://github.com/devenjarvis/lathe
145•devenjarvis•7h ago•31 comments

You'll never guess who made the first wireless telephone

https://signoregalilei.com/2026/05/31/youll-never-guess-who-made-the-first-wireless-telephone/
8•surprisetalk•3d ago•0 comments

Anthropic, please ship an official Claude Desktop for Linux

https://github.com/anthropics/claude-code/issues/65697
332•predkambrij•6h ago•178 comments

Proliferate (YC S25) is hiring to building open source Codex

https://www.ycombinator.com/companies/proliferate/jobs/L3copvK-founding-engineer
1•pablo24602•2h ago

Backrest – a web UI and orchestrator for restic backup

https://github.com/garethgeorge/backrest
33•flexagoon•5d ago•2 comments

My automated doubt development process

https://www.alexself.dev/blog/automated-doubt
5•aself101•51m ago•6 comments

Podman 6: machine usability improvements (2025)

https://blog.podman.io/2025/10/podman-6-machine-usability-improvements/
64•daesorin•5h ago•5 comments

Vitamin D3 During Pregnancy and Cognitive Performance at 10 Years

https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2849122
168•supermatou•4h ago•75 comments

Win16 Memory Management

http://www.os2museum.com/wp/win16-memory-management/
118•supermatou•2d ago•58 comments

Show HN: Kyushu – A self-hostable WASM sandbox for JavaScript workers

https://kyushu.dev/
61•le_chuck•11h ago•24 comments

The curious case of low-protein diets

https://knowablemagazine.org/content/article/living-world/2026/low-protein-diet-animals-live-longer
13•curmudgeon22•32m ago•0 comments

The Secret Life of Circuits with lcamtuf / Michał Zalewski (Audio Interview)

https://theamphour.com/725-the-secret-life-of-circuits-with-lcamtuf-michal-zalewski/
54•ChrisGammell•3d ago•5 comments

Public Domain Image Archive

https://pdimagearchive.org/
221•davidbarker•18h ago•31 comments

My Software North Star

https://kristoff.it/blog/north-star/
184•kristoff_it•3d ago•112 comments

Speculative KV coding: losslessly compressing KV cache by up to ~4×

https://fergusfinn.com/blog/kv-entropy-coder/
126•kkm•3d ago•21 comments

There's no escaping it: an exploration of ANSI codes

https://blog.safia.rocks/2025/12/22/ansi-codes/
19•ankitg12•2d ago•5 comments

sqlite: A CGo-free port of SQLite/SQLite3

https://gitlab.com/cznic/sqlite
18•tosh•5h ago•3 comments

Valve P2P networking broken for more than 2 months

https://github.com/ValveSoftware/GameNetworkingSockets/issues/398
246•babuskov•15h ago•123 comments

Tokenomics: Quantifying Where Tokens Are Used in Agentic Software Engineering

https://arxiv.org/abs/2601.14470
156•Anon84•17h ago•65 comments

Symbolica 2.0: Programmable Symbols for Python and Rust

https://symbolica.io/posts/symbolica_2_0_release/
134•mmastrac•2d ago•11 comments

LLMs are eroding my software engineering career and I don't know what to do

https://human-in-the-loop.bearblog.dev/llms-are-eroding-my-software-engineering-career-and-i-dont...
655•poisonfountain•6h ago•611 comments

How Long Does It Take for a QQuickItem to Become Visible?

https://www.kdab.com/how-long-does-it-take-for-an-item-to-become-visible/
29•jandeboevrie•2d ago•1 comments

Field of clones: How horse replicas came to dominate polo

https://knowablemagazine.org/content/article/technology/2026/cloned-polo-horses
149•gscott•16h ago•69 comments

The gamers taking on the industry to stop it switching off games

https://www.bbc.com/news/articles/c8e8e7g0r82o
63•Brajeshwar•2h ago•64 comments