HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dima-quant
nimic
Python2026–2026
dima-quant / nimic

nimic

Nimic allows using pure Python as a systems language with AOT compilation. It provides systems-level functionality directly within CPython (backed by the built-in ctypes module), while allowing the exact same code to compile Ahead-Of-Time (AOT) to an efficient native binary.

2Distinct people
3Mentions
0Explicit recommenders
42GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Nimic allows using pure Python as a systems language with AOT compilation. It provides systems-level functionality directly within CPython (backed by the built-in ctypes module), while allowing the exact same code to compile Ahead-Of-Time (AOT) to an efficient native binary.

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, 3:56:07 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 day3 dated mentions

Observed mentions: 2026-05-30 19:36:09 UTC to 2026-06-25 12:52:42 UTC.

012026-05-30 00:00:00 UTC to 2026-05-31 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 302026-05-31 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-01 00:00:00 UTC to 2026-06-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-02 00:00:00 UTC to 2026-06-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-03 00:00:00 UTC to 2026-06-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-04 00:00:00 UTC to 2026-06-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-05 00:00:00 UTC to 2026-06-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-06 00:00:00 UTC to 2026-06-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-07 00:00:00 UTC to 2026-06-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-08 00:00:00 UTC to 2026-06-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-09 00:00:00 UTC to 2026-06-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-10 00:00:00 UTC to 2026-06-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-11 00:00:00 UTC to 2026-06-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-12 00:00:00 UTC to 2026-06-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 122026-06-13 00:00:00 UTC to 2026-06-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-14 00:00:00 UTC to 2026-06-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-15 00:00:00 UTC to 2026-06-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-16 00:00:00 UTC to 2026-06-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-17 00:00:00 UTC to 2026-06-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-18 00:00:00 UTC to 2026-06-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-19 00:00:00 UTC to 2026-06-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-20 00:00:00 UTC to 2026-06-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-21 00:00:00 UTC to 2026-06-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-22 00:00:00 UTC to 2026-06-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-23 00:00:00 UTC to 2026-06-24 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-06-24 00:00:00 UTC to 2026-06-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-25 00:00:00 UTC to 2026-06-26 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 25

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
May 302026-05-30 00:00:00 UTC2026-05-31 00:00:00 UTC110
May 312026-05-31 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 12026-06-01 00:00:00 UTC2026-06-02 00:00:00 UTC000
Jun 22026-06-02 00:00:00 UTC2026-06-03 00:00:00 UTC000
Jun 32026-06-03 00:00:00 UTC2026-06-04 00:00:00 UTC000
Jun 42026-06-04 00:00:00 UTC2026-06-05 00:00:00 UTC000
Jun 52026-06-05 00:00:00 UTC2026-06-06 00:00:00 UTC000
Jun 62026-06-06 00:00:00 UTC2026-06-07 00:00:00 UTC000
Jun 72026-06-07 00:00:00 UTC2026-06-08 00:00:00 UTC000
Jun 82026-06-08 00:00:00 UTC2026-06-09 00:00:00 UTC000
Jun 92026-06-09 00:00:00 UTC2026-06-10 00:00:00 UTC000
Jun 102026-06-10 00:00:00 UTC2026-06-11 00:00:00 UTC000
Jun 112026-06-11 00:00:00 UTC2026-06-12 00:00:00 UTC000
Jun 122026-06-12 00:00:00 UTC2026-06-13 00:00:00 UTC000
Jun 132026-06-13 00:00:00 UTC2026-06-14 00:00:00 UTC000
Jun 142026-06-14 00:00:00 UTC2026-06-15 00:00:00 UTC000
Jun 152026-06-15 00:00:00 UTC2026-06-16 00:00:00 UTC000
Jun 162026-06-16 00:00:00 UTC2026-06-17 00:00:00 UTC000
Jun 172026-06-17 00:00:00 UTC2026-06-18 00:00:00 UTC000
Jun 182026-06-18 00:00:00 UTC2026-06-19 00:00:00 UTC000
Jun 192026-06-19 00:00:00 UTC2026-06-20 00:00:00 UTC000
Jun 202026-06-20 00:00:00 UTC2026-06-21 00:00:00 UTC000
Jun 212026-06-21 00:00:00 UTC2026-06-22 00:00:00 UTC000
Jun 222026-06-22 00:00:00 UTC2026-06-23 00:00:00 UTC000
Jun 232026-06-23 00:00:00 UTC2026-06-24 00:00:00 UTC110
Jun 242026-06-24 00:00:00 UTC2026-06-25 00:00:00 UTC000
Jun 252026-06-25 00:00:00 UTC2026-06-26 00:00:00 UTC101

What Hacker News says

3 sources
> how do you handle that It looks like (please correct me, OP, if I'm wrong) it works the other way around: you use sized int types in Nimic code, and their semantics are emulated on the Python side. See here: https://github.com/dima-quant/nimic/blob/main/src/nimic/ntyp... So I'd say in Nimic Python you get Nim-style integer emulation when run from Python, keeping both paths consistent with each other - but breaking consistency with the rest of Python. Which is OK, I think, given it's explicitly a subset(s) of the language(s). It would be possible to make `int` transpile to some BigInt Nim implementation, but you'd need an external dependency for this, as they are not in Nim's stdlib. However, in the speed-focused context, I'm not sure if defaulting to BigInt every time the compiler sees an `: int` annotation would work well. It's a hard
Read the rest
decision to make. Curious what's the OP opinion here?
In Show HN: Nimic – Pure Python as a systems language with AOT compilation

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.