Critical Acclaim
Every serious software project eventually reaches an important milestone.
Architecture.
Tests.
Documentation.
Release automation.
Observability.
And then, if you are very lucky:
People on Reddit tell you it is garbage.
At that point, congratulations.
You have reviews.
Most people make the mistake of treating hostile comments as something to defend against.
They respond.
They explain.
They clarify.
They produce diagrams.
They write seven paragraphs beginning with:
"Actually..."
No.
That is exhausting.
I have a better idea.
Put the reviews on the website.
The Critics Have Spoken
I already have the screenshots.
Among the commentary were variations on:
"That's not how game engines work."
"This is a mess."
"This is garbage."
Beautiful.
Do you understand how difficult it is to get authentic testimonials?
Companies spend entire marketing budgets trying to coax customers into producing sentences like:
"This product transformed our workflow."
Boring.
Nobody remembers that.
But:
"This is garbage."
That has energy.
That has conviction.
That person felt something.
Marketing departments would kill for engagement like that.
Five Stars Are Cowardice
Imagine the GameEngine page.
Clean layout.
Documentation.
Architecture.
Examples.
Packages.
All the normal responsible engineering material.
Then suddenly:
Critical Acclaim
★☆☆☆☆
"That's not how game engines work."
★☆☆☆☆
"This is a mess."
★☆☆☆☆
"This is garbage."
— Also Reddit
No rebuttal.
No defensive footnote.
No seventeen-slide presentation explaining why the commenter misunderstood the architecture.
Just the reviews.
Mounted on the wall.
Polished.
Framed.
Displayed with pride.
Like movie-poster quotes, except the movie critics are furious and one of them thinks the projector is not technically a projector.
The Engine Continues to Be Rude
The inconvenient part is that the thing works.
This creates a philosophical problem.
If someone says:
"That's not how a game engine works."
and the game engine continues working, we now have competing theories.
Theory one:
The commenter possesses the One True Definition of Game Engine.
Theory two:
Reality did not receive the memo.
I am generally willing to let reality settle these disputes.
The engine runs.
The simulations run.
The tests run.
The deterministic behavior remains annoyingly deterministic.
The code does not stop in the middle of execution, read Reddit, become ashamed, and delete itself.
Frankly, that shows a lack of community engagement.
I Could Argue
I could explain that the engine is not trying to be Unity.
I could explain the simulation model.
I could explain why it has the architecture it has.
I could explain what problems it is solving.
I could explain that different engines can have different shapes because software categories are not handed down on stone tablets by graphics programmers.
I could do all that.
But there is a much funnier option.
Quote them accurately.
Link the project.
Let the reader decide what to make of it.
That is far more entertaining.
Testimonials Should Reveal Something
A normal testimonial says:
"I enjoyed this product."
Fine.
A hostile testimonial says:
"I encountered this project, developed an immediate theory about what it was allowed to be, and became emotionally invested enough to type about it."
That is information.
The project was not invisible.
It did not pass quietly through the timeline like another framework announcement nobody remembers twelve minutes later.
Somebody stopped.
Somebody looked.
Somebody objected.
Beautiful.
The engine has achieved irritation.
That is practically product-market fit.
Screenshot or It Didn't Happen
The best part is I do not have to invent any of this.
I have the screenshots.
Receipts.
Artifacts.
Historical records from the Great Reddit Game Engine Incident.
So when the testimonials go on the site, they can sit there exactly as they happened.
No polishing.
No fake quote from "John D., Senior Engineer."
No suspiciously enthusiastic customer who somehow speaks in corporate landing-page copy.
Real people.
Real irritation.
Real criticism.
Actual authentic human engagement.
At last.
Marketing.
The Proper Response to Criticism
Sometimes criticism is useful.
Sometimes it identifies a real problem.
Sometimes somebody sees something you missed.
Then you fix the thing.
Good.
Sometimes criticism is just somebody declaring that the object in front of them violates the category in their head.
Also useful.
That goes in Critical Acclaim.
This is not the same as pretending criticism does not matter.
It is simply refusing to perform the traditional internet ritual where every stranger receives a personal technical defense brief.
The code is available.
The documentation is available.
The behavior is available.
And now, thanks to Reddit, the testimonials are available too.
Honestly, I should send thank-you cards.
Without those comments, I would have had to write marketing copy myself.
And nobody wants that.
Well... why not?