frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
539•klaussilveira•9h ago•150 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
866•xnx•15h ago•525 comments

How we made geo joins 400× faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
73•matheusalmeida•1d ago•15 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
185•isitcontent•10h ago•21 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
186•dmpetrov•10h ago•82 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
296•vecti•12h ago•132 comments

Dark Alley Mathematics

https://blog.szczepan.org/blog/three-points/
72•quibono•4d ago•15 comments

Microsoft open-sources LiteBox, a security-focused library OS

https://github.com/microsoft/litebox
346•aktau•16h ago•168 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
341•ostacke•15h ago•90 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
437•todsacerdoti•17h ago•226 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
8•videotopia•3d ago•0 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
240•eljojo•12h ago•147 comments

What Is Ruliology?

https://writings.stephenwolfram.com/2026/01/what-is-ruliology/
4•helloplanets•4d ago•0 comments

Delimited Continuations vs. Lwt for Threads

https://mirageos.org/blog/delimcc-vs-lwt
15•romes•4d ago•2 comments

PC Floppy Copy Protection: Vault Prolok

https://martypc.blogspot.com/2024/09/pc-floppy-copy-protection-vault-prolok.html
43•kmm•4d ago•3 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
378•lstoll•16h ago•253 comments

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
222•i5heu•12h ago•166 comments

Show HN: ARM64 Android Dev Kit

https://github.com/denuoweb/ARM64-ADK
14•denuoweb•1d ago•2 comments

Why I Joined OpenAI

https://www.brendangregg.com/blog/2026-02-07/why-i-joined-openai.html
94•SerCe•5h ago•77 comments

Show HN: R3forth, a ColorForth-inspired language with a tiny VM

https://github.com/phreda4/r3
62•phreda4•9h ago•11 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
162•limoce•3d ago•82 comments

I spent 5 years in DevOps – Solutions engineering gave me what I was missing

https://infisical.com/blog/devops-to-solutions-engineering
128•vmatsiiako•14h ago•55 comments

Introducing the Developer Knowledge API and MCP Server

https://developers.googleblog.com/introducing-the-developer-knowledge-api-and-mcp-server/
38•gfortaine•7h ago•11 comments

Zlob.h 100% POSIX and glibc compatible globbing lib that is faste and better

https://github.com/dmtrKovalenko/zlob
6•neogoose•2h ago•2 comments

Understanding Neural Network, Visually

https://visualrambling.space/neural-network/
261•surprisetalk•3d ago•35 comments

Female Asian Elephant Calf Born at the Smithsonian National Zoo

https://www.si.edu/newsdesk/releases/female-asian-elephant-calf-born-smithsonians-national-zoo-an...
18•gmays•5h ago•2 comments

I now assume that all ads on Apple news are scams

https://kirkville.com/i-now-assume-that-all-ads-on-apple-news-are-scams/
1030•cdrnsf•19h ago•428 comments

FORTH? Really!?

https://rescrv.net/w/2026/02/06/associative
55•rescrv•17h ago•19 comments

Show HN: Smooth CLI – Token-efficient browser for AI agents

https://docs.smooth.sh/cli/overview
84•antves•1d ago•60 comments

WebView performance significantly slower than PWA

https://issues.chromium.org/issues/40817676
19•denysonique•6h ago•3 comments
Open in hackernews

The x86 Interrupt List, aka “Ralf Brown's Interrupt List” (2018)

http://www.cs.cmu.edu/~ralf/files.html
104•surprisetalk•3mo ago

Comments

aforwardslash•3mo ago
Oh the memories :) I still have somewhere a dot-matrix printed copy of the list I used religiously in the 90's
peterfirefly•3mo ago
I remember looking at a print out of some of it in the late 80's and learning about the "list of lists", the critical section flag, and the alternate stack.
userbinator•3mo ago
This was, and for some purposes still is, one of the most useful documentation sets for the PC architecture. It's worth noting that Ralf himself isn't a specialist low-level programmer, as this came from an era when there was a far smaller divide between users, power users, and developers.
whizzter•3mo ago
Many hours spent reading this even if I was quite late to the party.
AndrewStephens•3mo ago
This was invaluable when I was tasked with writing a stay-resident boot loader just after the turn of the century. Even then, such information was considered arcane and Ralf Browns Interrupt List was much better than any official documentation I could find.
summa_tech•3mo ago
Long ago, before access to the Internet was cheap and plentiful, and way before search engines made finding this kind of information easy, this was a priceless find for an aspiring low-level programmer. All the (semi-)common PC hardware and software documented in one place.

Endless hours spent exploring VGA hardware registers and trying to apply them for cool visual effects. Learning how the then-new 32-bit Windows interacted with DOS extenders, and trying to make a homemade - very basic - operating system that could do it, too. The thrill of writing a Terminate and Stay Resident alarm clock, and having it finally not explode...

I have very fond memories of the Ralf Brown's Interrupt List.

jesuslop•3mo ago
Absolutely. Title says 2018 but it really comes from the dawn of pc. DOS was at 21h, and now linux system calls in x86 are INT 80h.
EarlKing•3mo ago
Linux system calls WERE 80h. If your code is still using an interrupt to access kernel functions then you've got problems. Syscall exists for the simple reason that interrupts are expensive.
kragen•3mo ago
Int 80h still works as well as ever on i386.
zeusk•3mo ago
What do you mean by that? Most syscalls are still interrupt based.
maggit•3mo ago
x86-64 introduced a `syscall` instruction to allow syscalls with a lower overhead than going through interrupts. I don't know any reason to prefer `int 80h` over `syscall` when the latter is available. For documentation, see for example https://www.felixcloutier.com/x86/syscall
messe•3mo ago
32 bit x86 also has sysenter/sysexit.
adrian_b•3mo ago
Only Intel. AMD had its own "syscall" instead of Intel's "sysenter" since the K6 CPU, so x86-64 has inherited that.

AMD's "syscall" corrects some defects of Intel's "sysenter", but unfortunately it introduces some new defects.

Details can be found in the Linux documentation, in comments by Linus Torvalds about the use of these instructions in the kernel.

adrian_b•3mo ago
While AMD syscall or Intel sysenter can provide a much higher performance than the old "int" instructions, both syscall and sysenter have been designed very badly, as explained by Linus himself in many places. It is extremely easy to use them in ways that do not work correctly, because of subtle bugs.

It is actually quite puzzling why both the Intel designers and the AMD designers have been so incompetent in specifying a "syscall" instruction, when such instructions, but well designed, had been included in many other CPU ISAs for many decades.

When not using an established operating system, where the implementation for "syscall" has been tested for many years and hopefully all bugs have been removed, there may be a reason to use the "int" instruction to transition into the privileged mode, because it is relatively foolproof and it requires a minimum amount of code to be handled.

Now Intel has specified FRED, a new mechanism for handling interrupts, exceptions and system calls, which does not have any of the defects of "int", "syscall" and "sysenter".

The first CPU implementing FRED should be Intel Panther Lake, to be launched by the end of this year, but surprisingly, recently when Intel has made a presentation providing information about Panther Lake no word was said about FRED, even if this is expected to be the greatest innovation of Panther Lake.

I hope that the Panther Lake implementation of FRED is not buggy, which could have made Intel to disable it and postpone its introduction to a future CPU, like they have done many times in the past. For instance, the "sysenter" instruction was intended to be introduced in Intel Pentium Pro, by the end of 1995, but because of bugs it was disabled and not documented until Pentium II, in mid 1997, where it finally worked.

kaladin-jasnah•3mo ago
I recently found out about swi 0x123456 on ARM...
globalnode•3mo ago
many of the int 21h interrupts were virus install checks, telling for the future direction of microsoft?
anotherlab•3mo ago
I was using this before 2018. I used to write TSR applets for data collection. Knowing what interrupts were being was critical. It could mean the difference between your code working and it dying somewhere in expanded memory space.
burnt-resistor•3mo ago
Running disassembly on the system, VGA, and other add-in card BIOSes was often helpful. I recall figuring out how to cycle the palette faster than calling an interrupt, although it would still require vsync to prevent snow* and tearing.

* When updating the overscan region border color on some video cards DACs via direct port I/O, there would be random speckling of dots of previous and new colors like analog snow if synchronization to wait for the vertical blanking interval wasn't observed. This is the sort of shit emulation doesn't reproduce faithfully. It sometimes took having access to a lot of hardware to verify a program doing hardware-specific VGA tweaks worked correctly.

OCTAGRAM•3mo ago
There was unloved informatics in school and loved informatics at home. Unloved informatics consisted of graph flow optimizations. Loved informatics consisted of EGA programming and IRQ interrupt handling for multiple keypress detection and other stuff. Both informatics were in Turbo Pascal, but in sport olympiads going to interrupts or assembler was prohibited. Not that it was going to help, but… when olympiads end, I was going those doors again, and others did not. For others my loved informatics was door remaining shut.

20 years later it is an excercize to find a device where loved EGA programming tricks work. Only unloved informatics remained

int_19h•3mo ago
86Box is what you want for this kind of nostalgic programming, comrade.

Our teachers didn't know much about this stuff in school. The origin of my username here (and elsewhere) is from those classes at school; I once submitted an assignment that, under certain conditions, used inline asm in Turbo Pascal to do "INT 19h". Had to explain it later, but thankfully that particular teacher was more amused than offended.

FpUser•3mo ago
Was my bible at some point. Thanks for memories
wvenable•3mo ago
For those way to young to even know what this is, it's basically like MDN web documentation but for the DOS era. It was a community-maintained API reference for IBM PC hardware, DOS operating system, and other software.
NooneAtAll3•3mo ago
how much of this info has been subsumed by standardized uefi?
sim7c00•3mo ago
presumably nothing because its about old devices which dont have UEFI. that being said, i suppose you mean BIOS interrupts are silly and you dont really want to know about them these days. that's true. (theres more than bios stuff in this list tho).

for ppl looking to discover BIOS interrupts and their meanings in this list, follow the breadcrumb given and go and checkout EDK2.

notorandit•3mo ago
I too have spent hours of assembly code on PC hardware. My freshly downloaded copy of the interrupt list has always been at my (virtual) side when designing tests or libraries.

I think that has been one of the very first and largest information collection shared for free on the internet.

Kudos to Ralf Brown and whoever participated in keeping the list compete, accurate and timely.

gblargg•3mo ago
HTML version if you're just curious about what it looks like (all the links on the linked site seem to be zip files).

https://www.ctyme.com/rbrown.htm

djmips•3mo ago
When I came upon this list, and I don't remember how, I went from the The 97 Pound Weakling to a perfectly developed hacker. Seriously, it was a game changer and launched me into a game of catchup on the PC (I was a Apple II and C64 guy). I had so much fun at work with hacks but also making cool utilities.
stuaxo•3mo ago
Are there any interviews with Ralph Brown around?

It doesn't help that he's not the only RB.

burnt-resistor•3mo ago
Before there was PC Interrupts, there was the The Prgrammer's PC Sourcebook and similar available at specialized bookstores like Computer Literacy Bookshops. Regular bookstores would generally contain a few computer and programming titles, but they weren't necessarily the best references.
khedoros1•3mo ago
I'm not quite old enough to have needed to use this while writing my own software. But I've come back to it repeatedly while learning enough about the operation of DOS PCs to try my hand at reverse-engineering some games. That was at least 10 years ago. (It became clear that I'd bitten off more than I could chew, so no full game RE, but I documented a couple more file formats, wrote some file viewers, and learned a lot).
kazinator•3mo ago
I wonder how things were done in this thing: https://en.wikipedia.org/wiki/Sun386i

Was that DOS emulation running some real DOS that though it was invoking BIOS calls?

According to a HN submission 3 years ago, evidently, Peter Norton once wrote a book on the 386i:

https://www.amazon.co.uk/exec/obidos/ASIN/0136616127/ref%3Dn...

pharaohgeek•3mo ago
I remember the first time I found this list and playing around with it using Microsoft QuickBASIC. I couldn't believe how much more functionality it opened up to me. Mouse support. Graphics support. Fun memories!