Runloom
Languages and libraries
concurrency runtime
SHOW HN2026
47points
32comments
#1,260of 4,366 in 2026
Top 29%of 2026 by points
How HN took it
MixedNo clear lean
2 positive, 7 neutral or asking, 1 mixed, 5 critical, out of 15 comments about the project. Thread score -0.11.
Execution: 1 for, 4 againstDocs: 0 for, 1 againstIdea: 1 for, 0 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Impressive project
From 2 comments
This is a seriously impressive project. I see your pitch is M:N work-stealing across real cores on free-threaded 3.13t/3.14t which i think is only possible because nogil now…
ebeirne on HNNice! Having the history makes it easier to evaluate all the work you've put in, this is really impressive.
simonw on HN
Objections
Codebase too large and built in one commit, hard to trust
From 2 comments
This is an intimidating amount of code! 12,303 lines of C and 244,740 lines of Python, which looks to be a ton of monkeypatching plus huge amounts of test code. Only one commit…
simonw on HN250k lines of code in one commit is reason enough to disregard the project entirely, IMO. Vibe code if one wants, but that is just madness...
tfrancisl on HN
Monkeypatching is hard to maintain
From 1 comment
I propose separating #1 (the main API/SDK) into a separate core package. This will be easier, smaller, and cleaner to maintain, and will meet the needs of many users with new…
OutOfHere on HN
API and docs are messy
From 1 comment
great questions: I'd say start here for some basics https://github.com/robertsdotpm/runloom/blob/main/docs/quickstart.md…
Uptrenda on HN
Requests
Restore git history
From 2 comments
Whether they did that or had an LLM one shot it, I dont really care. Commit history is pretty important if you ever want to try fixing bugs or improving features in the future.
tfrancisl on HNIt might be worth recreating the git history from scratch in a way that excludes the markdown files - I've used Claude Code and OpenAI Codex to do that in the past with…
simonw on HN
Separate core API from monkeypatching
From 1 comment
I propose separating #1 (the main API/SDK) into a separate core package. This will be easier, smaller, and cleaner to maintain, and will meet the needs of many users with new…
OutOfHere on HN
Questions
How does it compare with gevent?
From 1 comment
How does this compare with gevent?
ksdme9 on HN
Why not just use Go?
From 2 comments
Why not just use Go?
hsnewman on HNWhy not just use Go, haha?
bigwhite on HN
Alternatives named
gevent
From 2 comments
How does this compare with gevent?
ksdme9 on HN> its hard to evaluate how much trust can be put in a project of this complexity at this early stage. I don't know, I'm not finding it hard to evaluate that at all. I've had bad…
CamouflagedKiwi on HN
Go
From 1 comment
Why not just use Go?
hsnewman on HN
Python threads and processes
From 1 comment
then why not just use threads/processes in python?
vorticalbox on HN