frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Deno Desktop

https://docs.deno.com/runtime/desktop/
69•GeneralMaximus•59m ago•15 comments

Did my old job only exist because of fraud?

https://david.newgas.net/did-my-old-job-only-exist-because-of-fraud/
441•advisedwang•8h ago•198 comments

Help I accidentally a wigglegram

https://lmao.center/blog/wiggle-accidents/
122•gregsadetsky•2d ago•21 comments

Apertus – Open Foundation Model for Sovereign AI

https://apertvs.ai/
318•T-A•9h ago•111 comments

Danish privacy activist Lars Andersen raided by police

https://twitter.com/LarsAnders1620/status/2068208864747540516#m
121•I_am_tiberius•1h ago•67 comments

Sakana Fugu

https://sakana.ai/fugu/
92•Finbarr•4h ago•48 comments

There is minimal downside to switching to open models

https://www.marble.onl/posts/cancel_claude.html
159•amarble•9h ago•115 comments

Memory Safe Inline Assembly

https://fil-c.org/inlineasm
81•pizlonator•2d ago•15 comments

Good results fine tuning a local LLM like Qwen 3:0.6B to categorize questions

https://www.teachmecoolstuff.com/viewarticle/fine-tuning-a-local-llm-to-categorize-questions
93•dev-experiments•7h ago•18 comments

Everything is logarithms

https://alexkritchevsky.com/2026/05/25/everything-is-logarithms.html
184•E-Reverance•9h ago•40 comments

How I play video games with spinal muscular atrophy

https://www.openassistivetech.org/how-i-actually-play-video-games-with-sma-the-tools-i-use-every-...
91•dannyobrien•3d ago•14 comments

Identity verification on Claude

https://support.claude.com/en/articles/14328960-identity-verification-on-claude
684•bathory•17h ago•578 comments

1983 Northern Telecom Commodore Phone

https://www.oldtelephoneroom.ca/1983-northern-telecom-commodore-phone/
43•arexxbifs•6h ago•12 comments

JSON-LD explained for personal websites

https://hawksley.dev/blog/json-ld-explained-for-personal-websites/
193•ethanhawksley•11h ago•57 comments

Beyond All Reason (Free Total Annihilation Inspired RTS)

https://www.beyondallreason.info
466•mosiuerbarso•19h ago•274 comments

Japanese verb conjugation the simple hard way

https://underreacted.leaflet.pub/3mmevu6woys27
74•valzevul•7h ago•92 comments

PowerFox Browser

https://powerfox.jazzzny.me/
111•thisislife2•9h ago•31 comments

Lisp in the Rust Type System

https://github.com/playX18/lisp-in-types/
35•quasigloam•2d ago•0 comments

Minecraft: Java Edition 26.2, the first version with Vulkan 1.2

https://www.minecraft.net/en-us/article/minecraft-java-edition-26-2
117•ObviouslyFlamer•4d ago•35 comments

Show HN: Teach your kids perfect pitch

https://github.com/paytonjjones/bsharp
107•paytonjjones•17h ago•63 comments

Prefer duplication over the wrong abstraction (2016)

https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction
459•rafaepta•14h ago•310 comments

Rent collections are down in New York

https://www.politico.com/news/2026/06/21/rent-collections-are-down-in-new-york-and-no-ones-sure-w...
68•JumpCrisscross•8h ago•252 comments

Show HN: Criterion Closet as a website – pull any of 1,247 films off the shelf

https://the-criterion-closet.vercel.app
82•olievans•1d ago•15 comments

The minimum viable unit of saleable software

https://brandur.org/minimum-viable-unit
149•brandur•13h ago•56 comments

Efficient C++ Programming for Modern C++ CPUs, Chapter 4/part 2

https://6it.dev/blog/infographics-operation-costs-in-cpu-clock-cycles-take-2-80736
34•birdculture•2d ago•3 comments

Show HN: Recall – Local project memory for Claude Code

https://github.com/raiyanyahya/recall
97•mateenah•9h ago•65 comments

Architecting a Conversion Engine in Swift

https://blog.minimal.app/conversion-engine/
22•arthurofbabylon•4d ago•4 comments

FDA advisors unanimously vote to approve Moderna's mRNA after agency drama

https://arstechnica.com/health/2026/06/fda-advisors-unanimously-vote-to-approve-modernas-mrna-aft...
169•worik•9h ago•88 comments

(How to Write a (Lisp) Interpreter (In Python)) (2010)

https://norvig.com/lispy.html
179•tosh•15h ago•59 comments

Shape Suffixes – Good Coding Style

https://medium.com/@NoamShazeer/shape-suffixes-good-coding-style-f836e72e24fd
8•sebg•3d 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•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.