Why I built a systems language from scratch.

Dear developer,

If you've made it this far, you probably know a little about Prismio already. Maybe you're thinking about trying it, maybe you just stumbled across the website, or maybe you're wondering why the hell someone would build another programming language in the first place.

Honestly, I wonder that sometimes too.

I've always had this habit of building things whenever something bothers me. I don't know if that's a good habit or a terrible one. When existing things don't work the way I want, my first thought is usually "fine, I'll build it myself."

That's basically how Prismio started.

I started working on it on August 24, 2024, and somehow, almost two years later, I'm still here.

The hardest part was never the code. It was answering one question: why?

Why another language? Why this design? Why should the compiler make this decision? Why should you trust what it's doing?

I kept coming back to one idea: the compiler should know where your data lives, and it should be able to explain itself. I don't want memory management to feel like something happening behind a curtain. I want the language and compiler to make those decisions understandable.

And Prismio isn't meant to stop at the language itself.

It's the first piece of a much bigger ecosystem I'm trying to build — the compiler, tooling, package manager, libraries, and everything around them designed to actually work together. This is just where that starts.

That said, Prismio is still early.

Some things are missing. Some things are rough. Some things will probably break. That's not something I want to hide from you. The roadmap is there, the source is open, and I'm trying to keep the whole thing as transparent as I can.

So if you're curious, give Prismio a try.

And if you do, I'd genuinely love to hear what happens — especially if something breaks, feels confusing, or makes you wonder "why did they do it this way?"

Those are the things that make it better.

Thanks for being here.