SwiftLatex, TexLyre and StellarLatex seem to be exactly this. Apparently this is something a lot of people want to see in the world, awesome stuff. I wonder what's the performance like between native XeLaTex and these wasm version and if it will be Overleaf's demise if these solutions can be easily self-hosted by organizations without worrying about the server getting bogged down by compile jobs.
You can do that with Onnx. You can graft the preprocessing layers to the actual model [1] and then serve that. Honestly, I already thought that ONNX (CPU at least) was already low level code and already very optimized.
@Author - if you see this is it possible to add comparisons (ie "vanilla" inference latencies vs timber)?
Anyways, I really appreciate you created the post. It’s pretty amazing that a project from a self-taught developer like me, who started in 2024, got so much attention.
What always came to mind for me is an “engine wiring harness”. It’s responsible for getting power and data to all the right places without having to manually route cables around the engine / car.
If you google an image of it, maybe it’ll make sense
As already mentioned, this is the noun use but also different connotations.
To my thinking, to orchestrate or steer suggests a conductor or driver, an outside entity providing direction. A master agent creating and directing subagents could reasonably be called an orchestrator.
A harness is what the horse wears to pull a cart, or what connects a pilot to a parachute and provides the controls to tug on and steer. It might provide guidance or capability, but not active direction. It's also a fairly common use in hardware ( a wire harness) and software (a testing harness) already.
Well, "Orchestrate" and "Steer" are verbs, while "Harness" is a noun. You need a noun here, not a verb, because the harness is not actively doing anything, it's just a set of constraints and a toolset.
