VectorRen exists for one simple reason: sometimes you just want to build something small, sharp, and joyful without turning it into a six‑month architecture summit. These games are vibe‑coded — not because we’re sloppy, but because building for the sheer fun of it is still allowed in this industry. Or at least it should be.
But here’s the twist: even when we’re messing around, we’re still teaching.
VectorRen is a living demonstration of how to build clean, intentional software in a world where Coding Assistants sit in the passenger seat. It’s proof that you can keep your craft sharp while letting the machine help with the heavy lifting.
This project is a reminder that the web is still a perfectly good place to make cool things, SVG is still criminally underrated, and good engineering doesn’t have to feel like homework.
Every VectorRen game is tiny on purpose.
No build chain. No dependency forest. No “install these 42 packages.”
Just a browser, an SVG, and a little JavaScript that minds its manners.
If it can’t load in a tab without a progress bar, it’s not VectorRen.
Modern browsers can do more than most engines from the 2000s.
Filters, transforms, audio, animation — it’s all there.
You don’t need a framework to draw a triangle and move it around.
VectorRen leans into what the browser already gives you for free.
SVG isn’t a file format. It’s a scene graph with opinions.
It’s debuggable. It’s inspectable. It’s honest.
You can pop open DevTools and see the entire world laid out like a wiring diagram.
VectorRen treats SVG as the renderer, the UI, and the aesthetic.
No shared engine. No monolithic framework.
Each game is its own little universe with its own rules and its own code.
If you want to build a racer next, you shouldn’t have to drag Asteroids’ physics along for the ride.
VectorRen is built so anyone can fork it, break it, fix it, or turn it into something weird.
If someone wants to learn how a game loop works, they should be able to read the code without needing a translator.
When you limit yourself to:
- SVG
- a few filters
- a handful of entities
- and a browser
…you end up making sharper decisions.
Constraints force clarity. Clarity makes good software.
Yes, we’re improvising.
Yes, we’re letting Copilot riff with us.
But the backbone is still:
- clear specs
- clean boundaries
- readable code
- predictable behavior
VectorRen shows that you can have fun and build things the right way.
Copilot can write code fast.
You still have to decide what the code should mean.
VectorRen is built to demonstrate that partnership:
- humans set the direction
- assistants accelerate the work
- the result is better than either could do alone
This is how modern software gets built — not by outsourcing thinking, but by amplifying it.
Vector graphics age like stone.
They’re crisp, scalable, and honest.
They don’t hide behind textures or shaders.
They show every line you meant to draw — and every line you didn’t.
VectorRen uses vectors because they force clarity and reward intention.
Because the web is the most accessible platform ever invented.
If you can open a tab, you can play.
If you can view source, you can learn.
If you can fork a repo, you can build your own.
No installs. No updates. No nonsense.
VectorRen is a reminder that joy and craft are not opposites.
You can build small things with big intention.
You can teach through clarity.
You can collaborate with assistants without losing your voice.
Build for fun.
Build with purpose.
Build with vectors.