Computers are often presented as general purpose tools for thought, creativity, communication or other sorts of human flourishing. And for many of us who work with them, computers are intrinsically interesting puzzle boxes.

But it's important to remember their historical origins and continuing role as practical tools of control. Specifically in two domains: financial and military. Computers aren't being misused or corrupted when you see them employed by accountants and generals. Those are the people who paid for the very first models. Those have always been the primary customers. The rest of us are the strangers misusing their tools.

@graydon it's sometimes a joke that we also populate with all our knowledge their pockets and databases. We have also become the target of their hate sometimes disguised as a benefit. Thanks for your words.
@graydon I've spent the past week trying to recover some engineering analysis software from the late 70s (sodium spray fire models for reactor safety). The generals and accountants got COBOL (it's a repurposed military logistics language), us questionable science/engineering types got FORTRAN for whatever the AEC, Air Force, or Army proving ground people wanted. At the end of the day, I see myself using the machines exactly as they were originally intended, at least some of the time.
@graydon okay, this is clearly the case with regards to military. How's it the case in terms of finance?

@vathpela IBM (nee CTR), NCR, Burroughs (nee American Arithmometer) etc. all have roots in accounting office equipment -- mechanical adding machines, tabulators, bookkeeping etc.

https://en.wikipedia.org/wiki/Accounting_machine

Accounting machine - Wikipedia

@graydon I guess I don't normally think either "office equipment" or "accounting" means "finance".
@vathpela I guess the distinction here is "financial professionals in non-financial businesses" (which you're saying is not-finance) vs. "financial professionals in financial businesses"? I'm including both, but I think the point stands even if you narrow to the latter category: banks and insurance companies dominate early computing customer lists.
@vathpela (Unless you're talking about the very-narrow sense in which the word is sometimes used, just to refer to capital-markets or investment-banking functions, which I am less-certain about the early-computing use of, at least the dealmaking parts if not the trading parts. But .. I don't think the slightly-broad use of the term "finance" covering the whole sector is particularly odd. See for example the Global Industry Classification Standard sector grouping for "financials")
@vathpela (And even within investment banking, it's worth noting that real-time stock-ticker feeding was a primary use-case that built out computer-adjacent peripheral mechanisms such as telegraph networks. Eg. the "thousand stock tickers installed in the offices of New York bankers and brokers" in the 1880s: https://en.wikipedia.org/wiki/Ticker_tape#History)
Ticker tape - Wikipedia

@graydon I would add "controller for industrial process", not as the "OG" but as the driver behind the second wave of them. In the early 80s, computerising control systems was not obvious. In the 90s it was and have been driving a lot of the embedded work and other uses.
@graydon this (among other things) is why I identify as 'a weapon' myself.

@graydon

The street finds its own uses for things.

@graydon True! Interestingly, it seems like our tools have adapted a fair bit because when I went back to use Fortran for HPC stuff I realized how great it is for physics & engineering
@agocke physics & engineering are very popular subjects in the military.
@graydon yup. And I'd rather do ballistics in fortran than C

Hi, I know it may seem strange to message you from a new account. I’m reaching out to let you know that we’ve launched a coin that directs 100% of its fees to your GitHub account as a form of appreciation for building Rust, which made Solana possible. So far, we’ve raised $160, and that amount will continue to grow over time.

https://github.com/graydon/rust

I understand this might sound suspicious, but I’m happy to explain everything further via email or Twitter.

GitHub - graydon/rust: personal fork for work on rust language

personal fork for work on rust language. Contribute to graydon/rust development by creating an account on GitHub.

GitHub