INingve·Jul 4, 2019Submission
Nitrous: A JIT plug-in for dynamic systems
3 points · Open discussionnitrousjit
nitrous
HISTORICAL RECORD2019–2019
nitrousjit / nitrous · Not publicly available
nitrous
Discover this repository through its Hacker News conversations.
2Distinct people
2Mentions
0Explicit recommenders
What to know before exploring
What it is
A public description has not been verified.
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, 1:49:46 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 hour2 dated mentions
Observed mentions: 2019-07-03 22:25:53 UTC to 2019-07-04 15:53:30 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 |
|---|---|---|---|---|---|
| Jul 3, 22:00 | 2019-07-03 22:00:00 UTC | 2019-07-03 23:00:00 UTC | 1 | 0 | 1 |
| Jul 3, 23:00 | 2019-07-03 23:00:00 UTC | 2019-07-04 00:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 00:00 | 2019-07-04 00:00:00 UTC | 2019-07-04 01:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 01:00 | 2019-07-04 01:00:00 UTC | 2019-07-04 02:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 02:00 | 2019-07-04 02:00:00 UTC | 2019-07-04 03:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 03:00 | 2019-07-04 03:00:00 UTC | 2019-07-04 04:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 04:00 | 2019-07-04 04:00:00 UTC | 2019-07-04 05:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 05:00 | 2019-07-04 05:00:00 UTC | 2019-07-04 06:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 06:00 | 2019-07-04 06:00:00 UTC | 2019-07-04 07:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 07:00 | 2019-07-04 07:00:00 UTC | 2019-07-04 08:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 08:00 | 2019-07-04 08:00:00 UTC | 2019-07-04 09:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 09:00 | 2019-07-04 09:00:00 UTC | 2019-07-04 10:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 10:00 | 2019-07-04 10:00:00 UTC | 2019-07-04 11:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 11:00 | 2019-07-04 11:00:00 UTC | 2019-07-04 12:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 12:00 | 2019-07-04 12:00:00 UTC | 2019-07-04 13:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 13:00 | 2019-07-04 13:00:00 UTC | 2019-07-04 14:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 14:00 | 2019-07-04 14:00:00 UTC | 2019-07-04 15:00:00 UTC | 0 | 0 | 0 |
| Jul 4, 15:00 | 2019-07-04 15:00:00 UTC | 2019-07-04 16:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
2 sourcesI'm working on something that could be applicable to this! There seem to be many areas that would benefit from a pluggable JIT engine, so I started building one: https://github.com/nitrousjit/nitrous/
It's designed to analyze and optimize existing codebases. So far it's produced some pretty decent speedups on the Python interpreter, though with a big drawback of very high compilation times due to using LLVM.
Let me know what you think or if you have performance-sensitive programs that you think would benefit from a low-investment JIT.
In It’s Time for a Modern Synthesis Kernel