In 2000 I was working on static scheduling for heterogeneous architectures. Since then I’ve spent my time in data center networking and distributed systems.
There’s a lot of energy now around heterogeneous compute. Most of the talk is about making exotic hardware programmable - Mojo and related work fit that story. That work matters. It still leaves a gap: how compute gets found, reserved, coordinated, and paid for across a loose network of different machines.
Programmable flops aren’t the same as economically addressable flops.
In other words: a compute market. DCP (Distributive Compute Platform, from Distributive) is an example: jobs go out, workers compete, execution lands wherever the network can place it—from a browser tab to a rack of GPUs, or a moving Tesla.
What I don’t see yet is a straight line from languages like Mojo into that world.
So I built a small bridge: a Mojo→JavaScript transpiler that can ship work to DCP from the browser. The JS isn’t the thesis; it’s a way to show Mojo-originated for-loops unrolled across a distributed compute economy.
Prototype: https://exergy-connect.github.io/mojo-js/web/dcp.html
Closing that gap for real isn’t a weekend hack. It sits between the language/runtime stack and the coordination and economics layer, and it probably needs serious alignment—e.g. between Modular-style runtimes and systems like DCP.
Without something in that slot, heterogeneous compute stays fenced in: either one runtime, or one facility.
With it, the fence is optional.
I’m interested in how people building Mojo and nearby stacks picture that middle layer—as infrastructure, as protocol, or as something else entirely.