frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

US vs. Google amicus curiae brief of Y Combinator in support of plaintiffs [pdf]

https://storage.courtlistener.com/recap/gov.uscourts.dcd.223205/gov.uscourts.dcd.223205.1300.1.pdf
253•dave1629•6h ago•358 comments

A Critical Look at MCP

https://raz.sh/blog/2025-05-02_a_critical_look_at_mcp
183•ablekh•5h ago•106 comments

Reverse engineering the 386 processor's prefetch queue circuitry

http://www.righto.com/2025/05/386-prefetch-circuitry-reverse-engineered.html
69•todsacerdoti•3h ago•25 comments

The Price of Remission

https://www.propublica.org/article/revlimid-price-cancer-celgene-drugs-fda-multiple-myeloma
34•danso•2d ago•11 comments

Show HN: Code Claude Code

https://github.com/RVCA212/codesys
64•sean_•5h ago•16 comments

Prolog's Eternal September (2017)

https://storytotell.org/prologs-eternal-september
53•Tomte•2d ago•33 comments

Comparison of C/POSIX standard library implementations for Linux

https://www.etalabs.net/compare_libcs.html
52•smartmic•5h ago•17 comments

Building Local-First Flutter Apps with Riverpod, Drift, and PowerSync

https://dinkomarinac.dev/building-local-first-flutter-apps-with-riverpod-drift-and-powersync
17•kobieps•3d ago•7 comments

Embracer Games Archive is preserving 75000 video games and needs contributions

https://embracergamesarchive.com/
105•draugadrotten•9h ago•49 comments

Vision Now Available in Llama.cpp

https://github.com/ggml-org/llama.cpp/blob/master/docs/multimodal.md
457•redman25•16h ago•101 comments

Adventures in Imbalanced Learning and Class Weight

http://andersource.dev/2025/05/05/imbalanced-learning.html
4•andersource•2d ago•0 comments

Private Japanese lunar lander enters orbit around moon ahead of a June touchdown

https://phys.org/news/2025-05-private-japanese-lunar-lander-orbit.html
177•pseudolus•3d ago•53 comments

Weave (YC W25) is hiring a founding engineer

https://www.ycombinator.com/companies/weave-3/jobs
1•adchurch•3h ago

React Three Ecosystem

https://www.react-three.org/
83•bpierre•7h ago•27 comments

A simple 16x16 dot animation from simple math rules

https://tixy.land
282•andrewrn•17h ago•62 comments

LTXVideo 13B AI video generation

https://ltxv.video/
189•zoudong376•8h ago•57 comments

'It cannot provide nuance': UK experts warn AI therapy chatbots are not safe

https://www.theguardian.com/technology/2025/may/07/experts-warn-therapy-ai-chatbots-are-not-safe-to-use
64•distalx•4h ago•64 comments

Gmail to SQLite

https://github.com/marcboeker/gmail-to-sqlite
267•tehlike•15h ago•80 comments

Intel: Winning and Losing

https://www.abortretry.fail/p/intel-winning-and-losing
64•rbanffy•9h ago•32 comments

Microsoft Teams will soon block screen capture during meetings

https://www.bleepingcomputer.com/news/microsoft/microsoft-teams-will-soon-block-screen-capture-during-meetings/
13•josephcsible•42m ago•17 comments

AI AI is draining water from areas that need it most

https://www.bloomberg.com/graphics/2025-ai-impacts-data-centers-water-data
17•mraniki•1h ago•8 comments

Not a three-year-old chimney sweep (2022)

https://fakehistoryhunter.net/2022/07/26/not-a-3-year-old-chimney-sweep/
82•nixass•13h ago•52 comments

The Deathbed Fallacy (2018)

https://www.hjorthjort.xyz/2018/02/21/the-deathbed-fallacy.html
206•mefengl•10h ago•97 comments

Lead Bullets (2011)

https://a16z.com/lead-bullets/
9•msukkarieh•4h ago•0 comments

Radxa Orion O6 brings Arm to the midrange PC (with caveats)

https://www.jeffgeerling.com/blog/2025/radxa-orion-o6-brings-arm-midrange-pc
71•goranmoomin•8h ago•55 comments

Show HN: Sprigman – Pac-Man Recreated in a Limited Tile Based JavaScript Engine

https://sprig.hackclub.com/share/X4EGvOFk1q8FroEPCj1G
10•kuberwastaken•2d ago•4 comments

Loss of dance and infant-directed song among the Northern Aché

https://www.cell.com/current-biology/fulltext/S0960-9822(25)00447-6
57•PaulHoule•3d ago•9 comments

Unique Games Conjecture

https://en.wikipedia.org/wiki/Unique_games_conjecture
9•surprisetalk•3h ago•1 comments

Detect and crash Chromium bots

https://blog.castle.io/detect-and-crash-chromium-bots-with-one-weird-trick-bots-hate-it/
101•avastel•3d ago•33 comments

'We Currently Have No Container Ships,' Seattle Port Says

https://www.newsweek.com/seattle-port-says-no-container-ships-tariffs-2069464
151•pseudolus•4h ago•55 comments
Open in hackernews

Reverse engineering the 386 processor's prefetch queue circuitry

http://www.righto.com/2025/05/386-prefetch-circuitry-reverse-engineered.html
69•todsacerdoti•3h ago

Comments

kens•3h ago
Author here. I hope you're not tired of the 386... Let me know if you have any questions.
neuroelectron•2h ago
Ok, now do 486.
kens•2h ago
I'm not as interested in the 486; I went stright to the Pentium: https://www.righto.com/2025/03/pentium-multiplier-adder-reve...
neuroelectron•2h ago
Fair enough. But why?
kens•2h ago
Because I saw a Navajo weaving of a Pentium and wanted to compare the weaving to the real chip: https://www.righto.com/2024/08/pentium-navajo-fairchild-ship...
neuroelectron•2h ago
I was only joking but I'm glad you have decided to take it seriously.
guerrilla•2h ago
I totally agree with your methodology. Stick to the classic leaps.
sitkack•2h ago
At what number of layers is it difficult to reverse engineer a processor from die photos? I would think at some point, functionality would be too obscured to able to understand the internal operation.

Do they ever put a solid metal top layer?

kens•2h ago
I've been able to handle the Pentium with 3 metal layers. The trick is that I can remove metal layers to see what is underneath, either chemically or with sanding. Shrinking feature size is a bigger problem since an optical microscope only goes down to about 800 nm.

I haven't seen any chips with a solid metal top layer, since that wouldn't be very useful. Some chips have thick power and ground distribution on the top layer, so the top is essentially solid. Secure chips often cover the top layer with a wire that goes back and forth, so the wire will break if you try to get underneath for probing.

sitkack•2h ago
I'll never tire of any analysis you do. But if you are taking requests, I'd love two chips.

The AMD 29000 series, a RISC chip with many architectural advances that eventually morphed into the K5.

And the Inmos Transputer, a Forth like chip with built in scheduling and networking, designed to be networked together into large systems.

https://en.wikipedia.org/wiki/AMD_Am29000

https://en.wikipedia.org/wiki/Transputer

kens•2h ago
Those would be interesting chips to examine, if I ever get through my current projects :-)
Zeetah•1h ago
If you are doing requests, I'd love to see the M68k series analyzed.
moosedev•16m ago
Another vote for the 68000 series :)
anyfoo•1h ago
Never, the 386 is way too important.
siliconunit•1h ago
very nice analysis! personally I'm a DEC alpha fan.. but I guess that's a too big endeavor.. (or maybe a selected portion?)
kens•1h ago
So many chips, so little time :-)
shihabkhanbd•1h ago
The two extra segment registers could be LDTR and TR, both of which hold a 16-bit selector index from the GDT (technically bit 2 is always zero).
lysace•1h ago
I miss those dramatic performance leaps in the 80s. 10x in 5 years, give or take.

Now we get like 2x in a decade (single core).

rasz•1h ago
There was no performance improvement clock for clock between 286 and 386 when running contemporary 16 bit code https://www.vogons.org/viewtopic.php?t=46350
lysace•1h ago
Ok.

I'm speaking of e.g. the leap between the IBM PC in 1981 and the Compaq 386 five years later.

vnorilo•14m ago
I wrote blitters in assembly back in those days for my teenager hobby games. When I could actually target the 386 with its dword moves, it felt blisteringly fast. Maybe the 386 didn't run 286 code much faster but I recall the chip being one of the most mind-blowing target machine upgrades I experienced. Much later I recall the FPU-supported quadword copy in 486dx and of course P6 meeting MMX in Pentium II. Good times.
lysace•6m ago
As did I :).

Imagine how it felt going from an 8086 @ 8 MHz to an 80486SX (the cheapo version without FPU) @ 33 MHz. With blazingly fast REP MOVSD over some form of proto local bus Compaq implemented using Tseng Labs ET4000/W32i.

myself248•1h ago
I remember reading about naive circuits like ripple-carry, where a signal has to propagate across the whole width of a register before it's valid. These seem like they'd only work in systems with very slow clocks relative to the logic itself.

In this writeup, something that jumps out at me is the use of the equality bus, and Manchester carry chain, and I'm sure there are more similar tricks to do things quickly.

When did the transition happen? Or were the shortcuts always used, and the naive implementations exist only in textbooks?

kens•1h ago
Well, the Manchester carry chain dates back to 1959. Even the 6502 uses carry skip too increment the PC. As word sizes became larger and transistors became cheaper, implementations became more complex and optimized. And mainframes have been using these tricks forever.
yukIttEft•56m ago
When are you going to implement the first electron-level 386 emulator?