frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Scorched Earth 2000 is back

http://www.scorch2000.com/web/
99•meshko•2h ago•32 comments

Linux gaming is faster because Windows APIs are becoming Linux kernel features

https://www.xda-developers.com/linux-gaming-is-getting-faster-because-windows-apis-are-becoming-l...
561•haunter•3d ago•358 comments

Setting up a free *.city.state.us locality domain (2025)

https://fredchan.org/blog/locality-domains-guide/
513•speckx•12h ago•163 comments

A History of IDEs at Google

https://laurent.le-brun.eu/blog/a-history-of-ides-at-google
290•laurentlb•4d ago•210 comments

Chess puzzle I found in my dad's old book

https://ardoedo.it/kempelen/
103•Eswo•2d ago•29 comments

The Emacsification of Software

https://sockpuppet.org/blog/2026/05/12/emacsification/
209•rdslw•19h ago•148 comments

Princeton mandates proctoring for in-person exams, upending 133 year precedent

https://www.dailyprincetonian.com/article/2026/05/princeton-news-adpol-proctoring-in-person-exami...
271•bookofjoe•6h ago•373 comments

Marco Polo: Finding a friend with only distance and motion

https://www.jackhogan.me/blog/marco-polo
42•jackhogan11•2d ago•5 comments

Twin brothers wipe 96 government databases minutes after being fired

https://arstechnica.com/tech-policy/2026/05/drop-database-what-not-to-do-after-losing-an-it-job/
324•jnord•1d ago•240 comments

Xs of Y – roguelike that names itself every run. Written in 4kLoC

https://github.com/nooga/xsofy
163•andsoitis•3d ago•70 comments

Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration

https://www.tryardent.com/
74•vc289•9h ago•32 comments

AEPs: API Enhancement Proposals

https://github.com/aep-dev/aeps
7•nateb2022•1d ago•1 comments

The US is winning the AI race where it matters most: commercialization

https://avkcode.github.io/blog/us-winning-ai-race.html
167•akrylov•12h ago•474 comments

S-100 Virtual Workbench

https://grantmestrength.github.io/S100/
106•rbanffy•11h ago•20 comments

Reverting the incremental GC in Python 3.14 and 3.15

https://discuss.python.org/t/reverting-the-incremental-gc-in-python-3-14-and-3-15/107014
206•curiousgal•4d ago•80 comments

Show HN: Needle: We Distilled Gemini Tool Calling into a 26M Model

https://github.com/cactus-compute/needle
644•HenryNdubuaku•1d ago•184 comments

A sentimental tour of late 1990s and early 2000s hacking tools

https://andreafortuna.org/2026/05/13/amarcord/
49•speckx•8h ago•16 comments

The Age of the Amplifier

https://www.construction-physics.com/p/the-age-of-the-amplifier
11•surprisetalk•1d ago•1 comments

Tell HN: Dont use Claude Design, lost access to my projects after unsubscribing

189•pycassa•5h ago•62 comments

Preserving Fisher-Price Pixter

https://dmitry.gr/?r=05.Projects&proj=37.%20Pixter
213•dmitrygr•2d ago•44 comments

Meta won't let you block its AI account on Threads

https://www.theverge.com/tech/929091/meta-ai-threads-account-block
123•logickkk1•6h ago•55 comments

After 3 decades of splendid scientific communication, this one's for you, Ned

https://www.adn.com/alaska-news/science/2026/05/08/after-3-decades-of-splendid-scientific-communi...
15•rolph•3d ago•0 comments

Leaving GitHub for Forgejo

https://jorijn.com/en/blog/leaving-github-for-forgejo/
537•jorijn•13h ago•285 comments

An idiot's guide to lead optimisation for proteins

https://magnusross.github.io/posts/protein-lead-optimisation-1/
145•magni121•2d ago•16 comments

I moved my digital stack to Europe

https://monokai.com/articles/how-i-moved-my-digital-stack-to-europe/
892•monokai_nl•15h ago•539 comments

Medicare's new payment model is built for AI. Most of the tech world has no idea

https://techcrunch.com/2026/05/12/medicares-new-payment-model-is-built-for-ai-and-most-of-the-tec...
64•brandonb•5h ago•39 comments

Comparing a 1980s memory map to the Raspi Pico

https://medium.com/@noborutakahashi/a-40-year-old-memory-map-comparable-to-todays-raspberry-pi-pi...
23•Schlagbohrer•3d ago•0 comments

Making the news available at no cost is a victory

https://www.sltrib.com/opinion/commentary/2026/05/12/just-days-tribune-reporting/
113•danso•7h ago•114 comments

Mystery Microsoft bug leaker keeps the zero-days coming

https://www.theregister.com/security/2026/05/13/disgruntled-researcher-releases-two-more-microsof...
23•e12e•1h ago•1 comments

Exploring 8 Shaft Weaving

https://algorithmicpattern.org/2026/03/11/exploring-8-shaft-weaving/
25•surprisetalk•2d ago•1 comments
Open in hackernews

A brief history of the numeric keypad

https://www.doc.cc/articles/a-brief-history-of-the-numeric-keypad
74•ThomPete•1y ago

Comments

card_zero•1y ago
> Picture the keypad of a telephone and calculator side by side. Can you see the subtle difference between the two without resorting to your smartphone? Don’t worry if you can’t recall the design.

Pfft, I have both on the table beside me. I live in a different timeline, I suppose.

tmtvl•1y ago
What subtle difference? On a telephone the numbers are in a circle, whereas on a calculator they're in a square. They're completely different.
thenthenthen•1y ago
I noticed ATM keypad in different countries use 1-2-3 or 7-8-9, I have yet to figure out if this is based on something, it seems fairly inconsistent with language/history/colonialism
throwup238•1y ago
7-8-9 is the “standard” for calculator keypads but Bell Labs (supposedly) did some research and found 1-2-3 was more intuitive for users when designing the touch tone telephone keypads. When ATMs were being designed, manufacturers in the US/Canada/Europe emulated the telephone keypad while manufacturers in Asia emulated the calculator keypad.
signal11•1y ago
These days you can get PIN-capable card-readers with touchscreens. Some of these models randomize the button layout, which can be interesting to those who rely on muscle memory to type their PIN. Especially given that some shops have the readers physically attached or secured, so you have to type the PIN at an odd angle.

Some examples here[1].

[1] https://ux.stackexchange.com/questions/144937/why-do-some-ne...

AStonesThrow•1y ago
As I was briefly a beneficiary of SNAP EBT ("Food Stamps") I was subjected to the process of managing that debit card. When checking out, for example from Walmart.com, a popup would appear so that the user can input his PIN.

The popup was served by the SNAP EBT provider, and it would randomize the PIN number pad. So indeed, you couldn't rely on muscle memory to input your PIN because the number pad changed every time input was requested. It seemed that the mouse was also required for this input, rather than the keyboard.

userbinator•1y ago
Relatedly, TV remote controls seem to have settled on the telephone layout with 1 in the top left.

I have also used a few kiosks with a keyboard that has its physical keys arranged in alphabetical order, which is just as confusing.

rmccue•1y ago
Seems reasonable to have the most frequently used numbers close to the user; I wonder if there might be something of Benfold’s law involved, where lower digits are more frequently used. https://en.wikipedia.org/wiki/Benford%27s_law
EvanAnderson•1y ago
That's my intuition. I spent a lot of time entering stacks of checks into 10-key calculators at my family's businesses growing up in the late 80s and mid-90s. Most entry used the bottom two rows of digits (the zero, double-zero, and 1-3)-- a lot of $10, $20, and $30 checks.
abanana•1y ago
A line early on in the article caught my eye:

> they serve the same functional goal — input numbers

Well, yes and no. Same as how, when it comes to data types, it often has to be pointed out to inexperienced developers that a phone "number" isn't a number in the mathematical sense - you can't add or multiply 2 of them together to get anything meaningful. It's an identifying string, that happens to use only digit characters. "123" in a telephone number is three individual unrelated digits, whereas "123" in a calculator represents the number one hundred and twenty-three.

So the functional goal isn't exactly the same. One is entering individual characters, but on the other you're more likely to be thinking "one hundred and twenty-three" as you type its digits.

It may or may not be related to the actual reason for the inversion of layout, but the subtle difference felt like a (possibly minor) error in the initial premise.

ztetranz•1y ago
It's sounds silly when the Android auto in my car reads a text message. "Message from twenty four thousand, five hundred and thirty nine ..."
Cordiali•1y ago
Tangentially related, when websites mess up the digit grouping in phone number input fields, I've noticed it becomes quite hard to read. Must be a headache to get it right though, because it's a convention that changes from country to country, but it's easily worse than not grouping the digits.
toast0•1y ago
Not that it's always right, but Google's libphonenumber has formatting rules for phone numbers that work pretty well. But you need to know the right country, which isn't always easy; people may enter a local number and the site context isn't always enough to know what country is implied.
tekla•1y ago
> Picture the keypad of a telephone and calculator side by side. Can you see the subtle difference between the two without resorting to your smartphone?

I sometimes wonder if people have ever used Excel to calculate anything ever

wtallis•1y ago
It's possible that at this point, a majority of the people who have ever used Excel to calculate anything have done so on a laptop that doesn't even have a numeric keypad. Certainly, that fraction of the cumulative historical Excel user base has been growing.
cduzz•1y ago
I worked for a couple summers as a "relay operator"; in the USA there is (was? give the hateful time I suppose...) a law, "Americans with Disabilities Act" to the effect that people unable to do a thing should be able to do the thing. Roughly it means "people in wheelchairs should be able to access buildings" and "people unable to see should be able to read newspapers" and "people unable to hear should be able to talk on the telephone." and so on.

The "let people unable to hear talk on the phone" accommodation was to provide actual teletype machines to people who can't hear (at the time, many of these devices were some hideous 75 baud 6 bit monsters where there were limited punctuation and only upper case); the phone company would then also run a service where they had operators (I was one, for a couple summers) where people would call this service and that service would act as a bridge (or, "relay") to the other kind of device. So deaf people could order pizza, teenagers could call their friends and talk about teenager stuff, etc.

Specific to this conversation, the "relay operator" setup was a telephone system billing computer (that would also setup the phone call) and a standard terminal that'd interface with the person with the TTY. There were 2 800 numbers; one to connect to a TTY and one to connect to my ears; people would connect and ask to talk to a peer, and I'd enter the billing / call info into the phone computer, then actually do the talking on the terminal.

Each of these systems had a very distinct keyboard (the phone co keyboard had deep wells on the home keys; the terminal had "normal" nubs on the home keys), and I spent a ton of time entering phone numbers on the phone co's billing computer, with my right hand. To this day, my right hand touch-types "phone company" numbers and normal "ten key" (I did a lot of data entry at other points in my life) with my left hand.

[edit]

oh -- these things, though "ttys" were called "TDD" or "TTD" or some silly name to imply they were for deaf people, though they were just ttys; the cooler kids, calling that relay number, had 300 or 1200 or even 2400bps modems; I think that's as fast as the phoneco's relay terminal went, though)

GA

crazygringo•1y ago
The article doesn't make it explicit, but from the facts it presents it seems like the fundamental difference between the numeric keypad and telephone keypad is:

- With the numeric keypad, you want an extra-large 0 at the bottom that can be operated with your thumb, because zeros are so disproportionately common in real-life numbers like prices. And smaller numbers are used more than larger numbers, so you put the smaller numbers closer to the 0 so you have to reach the least, and wind up with 7-8-9 at the top.

- With dialing phone numbers, zeros aren't more frequent -- in fact they're less because phone numbers can't start with them (in the US). For local numbers, all digits 1-9 are used with approximately equal frequency. So the keypad starts with a natural numeric order of 1-2-3 at the top in reading order, and puts 0 at the bottom since it feels weird to start counting with zero (just like QWERTY keyboards start with 1, and puts 0 after 9), and because it has the special function of calling the operator.

So there seems to be an actual logic to it.

gitroom•1y ago
Man, reading all this makes my brain itch, I still mess up on ATM keypads if the layout flips. You think people just adapt even if it never makes sense, or does frustration actually change design over time?
teo_zero•1y ago
Interesting research. Now I want an article about why in the top row of all computer keyboards 0 is right of 9 instead of left of 1.