HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
matheuscamarques
pon_beam
Erlang2026–2026
matheuscamarques / pon_beam

pon_beam

PON-BEAM is a complete re-architecture of the Erlang/OTP Virtual Machine (ERTS — Erlang Run-Time System) using the Notification-Oriented Paradigm (PON)

4Distinct people
5Mentions
0Explicit recommenders
57GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

PON-BEAM is a complete re-architecture of the Erlang/OTP Virtual Machine (ERTS — Erlang Run-Time System) using the Notification-Oriented Paradigm (PON)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval5 dated mentions

Observed mentions: 2026-08-05 17:10:17 UTC to 2026-08-10 05:11:44 UTC.

0122026-08-05 12:00:00 UTC to 2026-08-05 18:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsAug 5, 12:002026-08-05 18:00:00 UTC to 2026-08-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-06 00:00:00 UTC to 2026-08-06 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-06 06:00:00 UTC to 2026-08-06 12:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-08-06 12:00:00 UTC to 2026-08-06 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-06 18:00:00 UTC to 2026-08-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-07 00:00:00 UTC to 2026-08-07 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-07 06:00:00 UTC to 2026-08-07 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-07 12:00:00 UTC to 2026-08-07 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-07 18:00:00 UTC to 2026-08-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 7, 18:002026-08-08 00:00:00 UTC to 2026-08-08 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-08 06:00:00 UTC to 2026-08-08 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-08 12:00:00 UTC to 2026-08-08 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-08 18:00:00 UTC to 2026-08-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-09 00:00:00 UTC to 2026-08-09 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-09 06:00:00 UTC to 2026-08-09 12:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-08-09 12:00:00 UTC to 2026-08-09 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-09 18:00:00 UTC to 2026-08-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-10 00:00:00 UTC to 2026-08-10 06:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 10, 00:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 5, 12:002026-08-05 12:00:00 UTC2026-08-05 18:00:00 UTC211
Aug 5, 18:002026-08-05 18:00:00 UTC2026-08-06 00:00:00 UTC000
Aug 6, 00:002026-08-06 00:00:00 UTC2026-08-06 06:00:00 UTC000
Aug 6, 06:002026-08-06 06:00:00 UTC2026-08-06 12:00:00 UTC110
Aug 6, 12:002026-08-06 12:00:00 UTC2026-08-06 18:00:00 UTC000
Aug 6, 18:002026-08-06 18:00:00 UTC2026-08-07 00:00:00 UTC000
Aug 7, 00:002026-08-07 00:00:00 UTC2026-08-07 06:00:00 UTC000
Aug 7, 06:002026-08-07 06:00:00 UTC2026-08-07 12:00:00 UTC000
Aug 7, 12:002026-08-07 12:00:00 UTC2026-08-07 18:00:00 UTC000
Aug 7, 18:002026-08-07 18:00:00 UTC2026-08-08 00:00:00 UTC000
Aug 8, 00:002026-08-08 00:00:00 UTC2026-08-08 06:00:00 UTC000
Aug 8, 06:002026-08-08 06:00:00 UTC2026-08-08 12:00:00 UTC000
Aug 8, 12:002026-08-08 12:00:00 UTC2026-08-08 18:00:00 UTC000
Aug 8, 18:002026-08-08 18:00:00 UTC2026-08-09 00:00:00 UTC000
Aug 9, 00:002026-08-09 00:00:00 UTC2026-08-09 06:00:00 UTC000
Aug 9, 06:002026-08-09 06:00:00 UTC2026-08-09 12:00:00 UTC110
Aug 9, 12:002026-08-09 12:00:00 UTC2026-08-09 18:00:00 UTC000
Aug 9, 18:002026-08-09 18:00:00 UTC2026-08-10 00:00:00 UTC000
Aug 10, 00:002026-08-10 00:00:00 UTC2026-08-10 06:00:00 UTC110

What Hacker News says

5 sources
Hi HN, I built PON-BEAM, a heavily modified version of the Erlang/OTP 30 virtual machine. I wanted to eliminate the O(N) selective receive bottleneck and the CPU-heavy scheduler spinlocks by introducing a reactive, event-driven notification mesh at the C level (using epoll/eventfd). However, changing how the Erlang scheduler and garbage collector handle state transitions is notoriously dangerous and prone to lost wakeups or deadlocks. To make this viable, I had to formally prove the new architecture. I used a 4-pillar verification pipeline: TLA+ / TLC to model the non-blocking invariants of the new scheduler and mailbox. Coq for mechanized proofs of the Tri-Color garbage collection propagation. Frama-C / ACSL for C source-level memory safety and loop termination. PropEr for stateful equivalence testing against the baseline OTP 30. The res
Read the rest
ult is a VM that maintains exact Erlang semantics but achieves O(1) mailbox reads and 0.0% idle CPU. It is a completely different way to think about VM design (based on the Notification-Oriented Paradigm). You can read the architectural breakdown and the formal proofs in the repo. Would love to discuss formal methods and VM design with this community. Repo: https://github.com/matheuscamarques/pon_beam
In Show HN: PON-BEAM re-architecture of the Erlang VM

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.