---
title: "Discussion on \"An Engine Inside the Engine\" | Hashnode"
description: "Discussion on \"An Engine Inside the Engine\". One Unity WebGL binary serves a lab player and a 3D scene editor. The trick was not unifying them — it was knowing which layer to share and which to leave alone."
url: "https://hashnode.com/posts/an-engine-inside-the-engine/6a7d37fc2066cf5a2251e884"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [An Engine Inside the Engine](https://boundarylayer.hashnode.dev/an-engine-inside-the-engine?utm_source=hashnode&utm_medium=feed)

One Unity WebGL binary serves a lab player and a 3D scene editor. The trick was not unifying them — it was knowing which layer to share and which to leave alone.

Aug 13 · 8 min read · boundarylayer.hashnode.dev  
Read the article

-   [#unity](https://hashnode.com/tag/unity)
-   [#unity3d](https://hashnode.com/tag/unity3d)
-   [#webgl](https://hashnode.com/tag/webgl)
-   [#architecture](https://hashnode.com/tag/architecture)
-   [#webassembly](https://hashnode.com/tag/webassembly)
-   [#javascript](https://hashnode.com/tag/javascript)

## Written by

[David Mkrtchian](https://hashnode.com/@davidmcarati)

@davidmcarati · Yerevan, Armenia

  
[View profile](https://hashnode.com/@davidmcarati)

Game Focused, Tech Guy

## Responses

Markdown supported · ⌘↵ to post

No responses yet.