When I founded The World Table, the goal was clear: reimagining digital interaction. But to achieve the scale we envisioned for Mythcore: Omniveil, our upcoming MMORPG, the standard architectural patterns of the last decade simply weren't going to cut it.
We needed a foundation that could handle thousands of entities without the browser breaking a sweat. That foundation is the Loom Engine.
The Architecture of Loom: Precision Over Abstraction
Most TypeScript developers reach for Classes and Inheritance by default. In the early days of Loom, we realized that the "OOP Tax" - memory fragmentation and garbage collection pressure - was our biggest bottleneck.
To build a high-performance 2D engine, I made the executive decision to pivot Loom toward Data-Oriented Design (DOD).
Why the shift?
Contiguous Memory: By using TypedArrays and a Struct-of-Arrays (SoA) approach, we keep our data tightly packed.
Bypassing the GC: Loom minimizes object instantiation in the main simulation loop. No new objects means no Garbage Collector spikes during critical gameplay.
Near-Native Throughput: We are seeing performance metrics that challenge the "TypeScript is slow" stigma, pushing the V8 engine to its absolute limits.
Mythcore: Omniveil - The Manifestation
Loom isn't just a library; it’s the heartbeat of Mythcore: Omniveil. Currently in pre-alpha, Mythcore is the proof of concept for everything we’re building at The World Table.
In our latest prototypes, we’ve successfully managed complex batch rendering and zero-allocation physics solvers. We’re proving that you can have the developer velocity of TypeScript with the raw power usually reserved for low-level languages.
The "Sadhaka" Mindset
Building an engine from scratch is a sadhana - a disciplined practice. It’s about stripping away the "easy" abstractions to find the performant truth underneath.
I’m excited to join the CoderLegion community to share more deep dives into the Loom Engine’s architecture, our work on authoritative networking, and the journey of bringing Mythcore to life.
If you’re interested in high-frequency systems, WebGL/WebGPU optimization, or the future of browser-based gaming, let’s talk.