frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

Nobody has a personality anymore: we are products with labels

https://www.freyaindia.co.uk/p/nobody-has-a-personality-anymore
93•drankl•2h ago•51 comments

Bitchat – A decentralized messaging app that works over Bluetooth mesh networks

https://github.com/jackjackbits/bitchat
42•ananddtyagi•56m ago•24 comments

Building the Rust Compiler with GCC

https://fractalfir.github.io/generated_html/cg_gcc_bootstrap.html
80•todsacerdoti•3h ago•2 comments

Intel's Lion Cove P-Core and Gaming Workloads

https://chipsandcheese.com/p/intels-lion-cove-p-core-and-gaming
51•zdw•2h ago•0 comments

Show HN: I wrote a "web OS" based on the Apple Lisa's UI, with 1-bit graphics

https://alpha.lisagui.com/
241•ayaros•6h ago•78 comments

Jane Street barred from Indian markets as regulator freezes $566 million

https://www.cnbc.com/2025/07/04/indian-regulator-bars-us-trading-firm-jane-street-from-accessing-securities-market.html
225•bwfan123•10h ago•122 comments

Data on AI-related Show HN posts

https://ryanfarley.co/ai-show-hn-data/
218•rfarley04•2d ago•126 comments

Centaur: A Controversial Leap Towards Simulating Human Cognition

https://insidescientific.com/centaur-a-controversial-leap-towards-simulating-human-cognition/
8•CharlesW•1h ago•3 comments

I extracted the safety filters from Apple Intelligence models

https://github.com/BlueFalconHD/apple_generative_model_safety_decrypted
249•BlueFalconHD•5h ago•155 comments

There's a COMPUTER inside my DS flashcart [video]

https://www.youtube.com/watch?v=uq0pJmd7GAA
7•surprisetalk•57m ago•0 comments

Opencode: AI coding agent, built for the terminal

https://github.com/sst/opencode
122•indigodaddy•7h ago•28 comments

Get the location of the ISS using DNS

https://shkspr.mobi/blog/2025/07/get-the-location-of-the-iss-using-dns/
255•8organicbits•12h ago•75 comments

Functions Are Vectors (2023)

https://thenumb.at/Functions-are-Vectors/
148•azeemba•9h ago•79 comments

I don't think AGI is right around the corner

https://www.dwarkesh.com/p/timelines-june-2025
133•mooreds•4h ago•160 comments

A non-anthropomorphized view of LLMs

http://addxorrol.blogspot.com/2025/07/a-non-anthropomorphized-view-of-llms.html
89•zdw•2h ago•73 comments

Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo

https://github.com/MrLesk/Backlog.md
75•mrlesk•5h ago•16 comments

Lessons from creating my first text adventure

https://entropicthoughts.com/lessons-from-creating-first-text-adventure
25•kqr•2d ago•1 comments

Swedish Campground: "There are too many Apples on the screen!"

https://www.folklore.org/Swedish_Campground.html
6•CharlesW•1h ago•0 comments

Crypto 101 – Introductory course on cryptography

https://www.crypto101.io/
22•pona-a•3h ago•2 comments

Curzio Malaparte's Shock Tactics

https://www.newyorker.com/books/under-review/curzio-malapartes-shock-tactics
4•mitchbob•3d ago•2 comments

Async Queue – One of my favorite programming interview questions

https://davidgomes.com/async-queue-interview-ai/
88•davidgomes•8h ago•70 comments

Metriport (YC S22) is hiring engineers to improve healthcare data exchange

https://www.ycombinator.com/companies/metriport/jobs/Rn2Je8M-software-engineer
1•dgoncharov•8h ago

Corrected UTF-8 (2022)

https://www.owlfolio.org/development/corrected-utf-8/
38•RGBCube•3d ago•25 comments

Hannah Cairo: 17-year-old teen refutes a math conjecture proposed 40 years ago

https://english.elpais.com/science-tech/2025-07-01/a-17-year-old-teen-refutes-a-mathematical-conjecture-proposed-40-years-ago.html
336•leephillips•9h ago•75 comments

Why English doesn't use accents

https://www.deadlanguagesociety.com/p/why-english-doesnt-use-accents
60•sandbach•3h ago•55 comments

The Broken Microsoft Pact: Layoffs and Performance Management

https://danielsada.tech/blog/microsoft-pact/
31•dshacker•2h ago•11 comments

Toys/Lag: Jerk Monitor

https://nothing.pcarrier.com/posts/lag/
46•ptramo•10h ago•36 comments

Mirage: AI-native UGC game engine powered by real-time world model

https://blog.dynamicslab.ai
17•zhitinghu•1d ago•11 comments

Collatz's Ant and Σ(n)

https://gbragafibra.github.io/2025/07/06/collatz_ant5.html
23•Fibra•7h ago•3 comments

Overclocking LLM Reasoning: Monitoring and Controlling LLM Thinking Path Lengths

https://royeisen.github.io/OverclockingLLMReasoning-paper/
48•limoce•12h ago•0 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•1mo ago

Comments

card_zero•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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.