News for hackers. Stuff that matters.
Re:$30M Raised to Redo the CPU by quilombodigital on Wednesday November 11, 2026 @12:30AM (#50450028)
Am I missing something?

I couldn't find any parallel constructs in the language. So, as I understand it, it's a regular language that gets compiled into a graph, and the runtime parallelizes the execution of that graph.

This factorial won't run any faster with more cores, since each step depends on the previous one:

  fn fat(n: N64) -> N64 {
    if n <= 1 {
      1
    } else {
      n * fat(n - 1)
    }
  }
This other version can run in parallel, but only because the algorithm was deliberately written that way:

  fn fat(n: N32) -> Nat {
    if n == 0 { 1 as Nat } else { prod(1, n) }
  }

  fn prod(lo: N32, hi: N32) -> Nat {
    if lo == hi {
      lo as Nat
    } else {
      let m = (lo + hi) / 2;
      let left = prod(lo, m);
      let right = prod(m + 1, hi);
      left * right
    }
  }
So the programmer still has to think about parallelism; the language just removes the need for threads and locks.

Also, as the graph grows, sequential dependencies still limit the speedup, and more cores means more data moving between them. How does the hardware deal with that?

Re:$30M Raised to Redo the CPU by nukanse on Wednesday November 11, 2026 @12:54AM (#50450134)
The factorial can be calculated using a Taylor series, whose individual terms can be calculated and summed in parallel.
Re:$30M Raised to Redo the CPU by martiancookbook on Wednesday November 11, 2026 @02:22AM (#50450609)
Bom dia, it's my understanding that there is no runtime. The hardware does all of the graph rewrites. If you look at their 'On Interaction Nets' post [1], it seems that part of the pitch is that many programs can be written 'naturally' and still parallelize well.

[1] https://tendrils.co/blog/2026-04-26/on-inets

Re:$30M Raised to Redo the CPU by quilombodigital on Wednesday November 11, 2026 @10:39PM (#50462779)
Hi, thanks, I initially understood that, but I gave a non parallelizable example to show that there sometimes it is serialized by design, but I agree that in theory "real world" examples should be more amenable to parallelization.

Looking forward to seeing how the hardware handles the cost of communication between cores.