NNnnx·Mar 25, 2026Submission
Iris – a C inference pipeline for image synthesis models
4 points · Open discussionantirez
iris.c
C2026–2026
antirez / iris.c
iris.c
Flux 2 image generation model pure C inference
4Distinct people
5Mentions
1Explicit recommenders
2.1KGitHub stars
What to know before exploring
What it is
Flux 2 image generation model pure C inference
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
Because I've played this game too many times before - I know that some people will find a hole in any example you show them. So before doing that work, I want to get a feel for…
simonw used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
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, 12:54:37 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 week5 dated mentions
Observed mentions: 2026-01-18 18:01:58 UTC to 2026-03-25 09:34:11 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jan 12 | 2026-01-12 00:00:00 UTC | 2026-01-19 00:00:00 UTC | 1 | 1 | 0 |
| Jan 19 | 2026-01-19 00:00:00 UTC | 2026-01-26 00:00:00 UTC | 0 | 0 | 0 |
| Jan 26 | 2026-01-26 00:00:00 UTC | 2026-02-02 00:00:00 UTC | 2 | 0 | 2 |
| Feb 2 | 2026-02-02 00:00:00 UTC | 2026-02-09 00:00:00 UTC | 0 | 0 | 0 |
| Feb 9 | 2026-02-09 00:00:00 UTC | 2026-02-16 00:00:00 UTC | 1 | 0 | 1 |
| Feb 16 | 2026-02-16 00:00:00 UTC | 2026-02-23 00:00:00 UTC | 0 | 0 | 0 |
| Feb 23 | 2026-02-23 00:00:00 UTC | 2026-03-02 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2 | 2026-03-02 00:00:00 UTC | 2026-03-09 00:00:00 UTC | 0 | 0 | 0 |
| Mar 9 | 2026-03-09 00:00:00 UTC | 2026-03-16 00:00:00 UTC | 0 | 0 | 0 |
| Mar 16 | 2026-03-16 00:00:00 UTC | 2026-03-23 00:00:00 UTC | 0 | 0 | 0 |
| Mar 23 | 2026-03-23 00:00:00 UTC | 2026-03-30 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
5 sourcesThat's a silly bar to ask for.
Chrome took at least a thousand man years i.e. 100 people working for 10 years.
I'm lowballing here: it's likely way, way more.
If ai gives 10x speedup, to reproduce Chrome as it is today would require 1 person working for 100 years, 10 people working for 10 years or 100 people working for 1 year.
Clearly, unrealistic bar to meet.
If you want a concrete example: https://github.com/antirez/flux2.c
Creator of Redis started this project 3 weeks ago and use Claude Code to vibe code this.
It works, it's fast and the code quality is as high as I've ever seen a C code base. Easily 1% percentile of quality.
Look at this one-shotted working implementation of jpeg decoder: https://github.com/antirez/flux2.c/commit/a14b0ff5c3b74c7660...
Now, it takes a skilled person to guide Claude Code to generate this but I have zer
Read the rest
o doubts that this was done at least 5x-10x faster than Antirez writing the same code by hand.
Because I've played this game too many times before - I know that some people will find a hole in any example you show them.
So before doing that work, I want to get a feel for if you're asking this question in good faith and have done any active looking yourself.
(My favorite two recent open source examples are https://simonwillison.net/2026/Jan/27/one-human-one-agent-on... and https://github.com/antirez/flux2.c)
In The Five Levels: From spicy autocomplete to the dark factoryHave you looked at antirez's code?
https://github.com/antirez/flux2.c
In Vibe coding kills open source