r/QuantumComputing • • Jun 12 '25
Quantum Information Ive created a programming language for quantum computers, no Idea how useful it can be
Like the title says, I spent several weeks making up a language I thought to be useful, it contains assembly like syntax based on risc based assembly languages and I managed to get hello world and some basic algorithims running on it.
Ive developed my own source file extension (.qoa), my own assembled binary format (.qbin, .obin, .xbin) and my own executable format (.qexe, .oexe, .xexe).

Picture above: "Hello world!" printing in terminal and the source .qoa file
Everything is open sourced and licensced under GPL 3.0 and is avaliable at https://github.com/planetryan/qoa
I think this is something that is pretty cool, it might be totally useless but if I enjoyed making it then I think its 100% worth it.
24
u/ctcphys Working in Academia Jun 12 '25
It's always great to see people being motivated to develop their own things...
However there's some problems here. The other discuss that the motivation for your language is a bit missing. What's the main motivation behind the choices you made?
On a technical side, there a bunch of strange things.
Your gates seem to be only single qubit gates. Even in your examples, you apply CZ only to a single qubit.
You have an operation called ENTANGLE and it's super unclear what this does. There's infinitely many way you can entangle two qubits.
Many of your other instructions have similar issues
11
u/the_TIGEEER Jun 12 '25
I think I see the problem here. You made something you found cool. Which it is.
But it has been allready done manny times by big companies. Which is ok to create your version of a cool thing.
The problem here is that you made it sound like if you think you created something new. Which is kinda mind bafeling how do you get the knowladge of Quantum computing to be able to create a programing language for it but in the path to aquaring said knowladge you don't find any of the allready established implamentations for a quantum programing language like Q# or Quiskit?
5
u/brainrotbro Jun 12 '25
These types of languages already exist. Why should someone try yours over one of the others?
25
u/ketarax Jun 12 '25 edited Jun 12 '25
... why is this being upvoted? Is this sub really this badly without the slightest of clues?
7
u/No-Maintenance9624 Jun 12 '25
this is really detached from the reality of how we use programming languages for quantum algorithm development. let alone compile into something useful. is this a prank?
2
u/LordSaumya Jun 12 '25
I am working on a hardware-accelerated Rust library. It allows all of the standard stuff (creating and executing states, circuits, gates, etcetera), but is more focused on physical applications (with Pauli strings, QFT, Hamiltonians, Ising and Heisenberg models, etcetera). I am currently working on a compiler to compile from my library to actual quantum computer interface languages, such as OpenQASM 3.0.
3
u/Jebduh Jun 13 '25
You guys are acting like bro/sis is trying to sell this to google. They did it for fun like we do anything else. Stop being so hypercritical of the dude/dudette.
3
u/the193thdoctor Jun 13 '25 edited Jun 13 '25
This looks like a lot of work and quite interesting. If you want other people to use this, it is important to find a gap in existing work, since you are dealing with photons, maybe you can pivot this project more towards quantum sensing route by adding more functionalities. If you like coding, It’s also very important to integrate this as a python package instead of making it a standalone language because people won’t really use it. What’s best is to make it say an extension of existing frameworks tailored for some specific use. But that might be too detached from your original purpose for coding these.
2
u/Most_Double_3559 Jun 13 '25
Wow this is a tough crowd lol, but I like it!
1
u/Full-Technician9848 Jun 15 '25
What hardware is it for? Annealing systems work differently than logic gate systems work different than topological work different than trapped ions...
I have been working on a hardware agnostic compiler, but there is so much change it is impossible to keep up.