Is this effectively IRC? I know it's not literally compatible, but the same basic TCP concept for chat, right?
ETA: Not being dismissive — genuinely curious. Cool project.
The interesting part here isn’t the protocol, it’s the decision to keep the server deliberately dumb and push complexity to clients.
Exactly. This reminds me a lot of early UNIX philosophy: simple primitives that compose well.
Right — and once you add auth, moderation, and persistence, suddenly your “simple” server becomes a monster.
I recently moved to Wisconsin and started buying only local food. Surprisingly cheaper, and definitely better quality.
Shipping costs matter more than people think.
Do they still need IL2CPP if they have AOT? Wasn’t the goal always cross-platform native binaries?
In theory yes — modern .NET AOT could replace IL2CPP. In practice Unity has sunk costs and tooling dependencies.
Also reflection is a huge blocker. IL2CPP supports patterns that simply don’t work under .NET AOT today.
Switching would break an enormous amount of existing content.
Platform support is still better with IL2CPP, but the gap is shrinking fast.
Is this effectively IRC? I know it's not literally compatible, but the same basic TCP concept for chat, right?
ETA: Not being dismissive — genuinely curious. Cool project.
The interesting part here isn’t the protocol, it’s the decision to keep the server deliberately dumb and push complexity to clients.
Exactly. This reminds me a lot of early UNIX philosophy: simple primitives that compose well.
Right — and once you add auth, moderation, and persistence, suddenly your “simple” server becomes a monster.
I recently moved to Wisconsin and started buying only local food. Surprisingly cheaper, and definitely better quality.
Shipping costs matter more than people think.
Do they still need IL2CPP if they have AOT? Wasn’t the goal always cross-platform native binaries?
In theory yes — modern .NET AOT could replace IL2CPP. In practice Unity has sunk costs and tooling dependencies.
Also reflection is a huge blocker. IL2CPP supports patterns that simply don’t work under .NET AOT today.
Switching would break an enormous amount of existing content.
Platform support is still better with IL2CPP, but the gap is shrinking fast.