Mirror of forum.nim-lang.org

13651 :: Nimony progress report -- part 5

• Araq (orginal) [2026-01-13T12:31:13+01:00] view original

  The progress of Nimony has slowed down significantly as we bring IC to Nim 2. However, there is still progress to report:

  • Nimony now produces NIF26 instead of NIF24.
  • I fixed a silly bug that caused Nimony to always parse NIF files into unused buffers. Now that it's been fixed Nimony is faster and consumes less memory. (I have no numbers though.)

  Furthermore the architecture changed to:

  
  Nimony (frontend) ---> NJ ------+---> C / C++
                         ^        |
                         |        +----> JS
                         |        |
  Nim 2 (frontend)  -----+        +----> native backend x86-64
                                  |
                                  +----> native backend ARM64
  Run

  So some development moved over to "NativeNif" which implements "NJ", is a new backend language to be targetted by both Nim 2 and Nimony.

---

• Hobbyman (orginal) [2026-01-13T18:28:34+01:00] view original

  Oh that's a good idea to create a common backend-node (if it is doable) to avoid double work. What does NJ stand for? No Joke? Or New Job :--)

  Nice old-style relagram by the way.

---

• Araq (orginal) [2026-01-13T18:31:23+01:00] view original

  It stands for "No jumps". There is no break/continue/goto whatsoever, instead so called "cfvars" are used. You can read about its benefits here but the name was changed from NJVL to NJ and I'm writing a new spec.

---