frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

X5.1 solar flare, G4 geomagnetic storm watch

https://www.spaceweatherlive.com/en/news/view/593/20251111-x5-1-solar-flare-g4-geomagnetic-storm-...
285•sva_•10h ago•81 comments

Bluetooth 6.2 – more responsive, improves security, USB comms, and testing

https://www.cnx-software.com/2025/11/05/bluetooth-6-2-gets-more-responsive-improves-security-usb-...
45•zdw•6d ago•18 comments

Laptops with Stickers

https://stickertop.art/main/
309•z303•1w ago•302 comments

Perkeep – Personal storage system for life

https://perkeep.org/
121•nikolay•3h ago•27 comments

.NET MAUI is coming to Linux and the browser

https://avaloniaui.net/blog/net-maui-is-coming-to-linux-and-the-browser-powered-by-avalonia
166•vyrotek•8h ago•130 comments

I didn't reverse-engineer the protocol for my blood pressure monitor in 24 hours

https://james.belchamber.com/articles/blood-pressure-monitor-reverse-engineering/
187•jamesbelchamber•9h ago•74 comments

Four strange places to see London's Roman Wall

https://diamondgeezer.blogspot.com/2025/11/odd-places-to-see-londons-roman-wall.html
126•zeristor•8h ago•33 comments

Why Nietzsche matters in the age of artificial intelligence

https://cacm.acm.org/blogcacm/why-nietzsche-matters-in-the-age-of-artificial-intelligence/
88•pseudolus•7h ago•54 comments

Problems with C++ exceptions

https://marler8997.github.io/blog/bjarne-fix-your-language/
47•signa11•1h ago•33 comments

The terminal of the future

https://jyn.dev/the-terminal-of-the-future
174•miguelraz•11h ago•85 comments

Pikaday: A friendly guide to front-end date pickers

https://pikaday.dbushell.com
190•mnemonet•16h ago•77 comments

A modern 35mm film scanner for home

https://www.soke.engineering/
179•QiuChuck•11h ago•132 comments

Heroku Support for .NET 10

https://www.heroku.com/blog/support-for-dotnet-10-lts-what-developers-need-know/
65•runesoerensen•9h ago•25 comments

The history of Casio watches

https://www.casio.com/us/watches/50th/Heritage/1970s/
209•qainsights•3d ago•107 comments

FFmpeg to Google: Fund us or stop sending bugs

https://thenewstack.io/ffmpeg-to-google-fund-us-or-stop-sending-bugs/
770•CrankyBear•12h ago•563 comments

My fan worked fine, so I gave it WiFi

https://ellis.codes/blog/my-fan-worked-fine-so-i-gave-it-wi-fi/
158•woolywonder•6d ago•57 comments

Scaling HNSWs

https://antirez.com/news/156
177•cyndunlop•17h ago•40 comments

Fixing LCD Screen Corruption of a Tektronix TDS220 Oscilloscope

https://tomverbeure.github.io/2025/11/03/TDS220-LCD-Corruption-Fix.html
17•groseje•1w ago•1 comments

We ran over 600 image generations to compare AI image models

https://latenitesoft.com/blog/evaluating-frontier-ai-image-generation-models/
135•kalleboo•13h ago•84 comments

The Department of War just shot the accountants and opted for speed

https://steveblank.com/2025/11/11/the-department-of-war-just-shot-the-accountants-and-opted-for-s...
170•ridruejo•16h ago•253 comments

A catalog of side effects

https://bernsteinbear.com/blog/compiler-effects/
92•speckx•11h ago•7 comments

iPhone Pocket

https://www.apple.com/newsroom/2025/11/introducing-iphone-pocket-a-beautiful-way-to-wear-and-carr...
480•soheilpro•21h ago•1182 comments

Agentic pelican on a bicycle

https://www.robert-glaser.de/agentic-pelican-on-a-bicycle/
70•todsacerdoti•11h ago•50 comments

Collaboration sucks

https://newsletter.posthog.com/p/collaboration-sucks
374•Kinrany•10h ago•206 comments

Hard drives on backorder for two years as AI data centers trigger HDD shortage

https://www.tomshardware.com/pc-components/hdds/ai-triggers-hard-drive-shortage-amidst-dram-squee...
18•pabs3•1h ago•11 comments

Meticulous (YC S21) is hiring to redefine software dev

https://jobs.ashbyhq.com/meticulous/3197ae3d-bb26-4750-9ed7-b830f640515e
1•Gabriel_h•10h ago

Learning to Model the World with Language

https://dynalang.github.io/
38•jxmorris12•5d ago•1 comments

Adk-go: code-first Go toolkit for building, evaluating, and deploying AI agents

https://github.com/google/adk-go
65•maxloh•11h ago•19 comments

Array-programming the Mandelbrot set

https://jcmorrow.com/mandelbrot/
69•jcmorrow•5d ago•9 comments

Terminal Latency on Windows (2024)

https://chadaustin.me/2024/02/windows-terminal-latency/
98•bariumbitmap•13h ago•77 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•6mo ago

Comments

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