Currently Proton is at v0.2.5. So it might feel weak. It is made by an indie developer not by a full company like gogpu. In v0.3(currently under development) however we will add tons of more features. Please do check them out.
Bro you can
Choose Sonic Pi if you need a mature, extensively documented system with a large community
Choose Aethra if you prefer a fresh, specialized language designed to make composing music easier, prioritizing readable, less technical code and coding pain
No problem I will tell you and after telling you I will also add a guide
AETHRA How to use it?
First go to the GitHub link I gave you in the post. Download AETHRA or clone it. After downloading go to the folder named 'AETHRA' then go to bin then RELEASE and then to Net 10 Windows Folder. You will get an exe named AETHRA v0.8. After that start your Music Journey. To get all it's commands go to the GitHub project and read the README. You will get a built in AETHRA script, if it is working you are ready to go!
People have been comparing it to Strudel, so I wanted to clearly explain the difference.
ÆTHRA vs Strudel (in short):
ÆTHRA is output-oriented: you write a script → run it → get a WAV file.
Strudel is performance-oriented: it’s browser-based live coding focused on real-time pattern manipulation.
Key differences:
Export
ÆTHRA has built-in WAV export (one click).
Strudel doesn’t natively export audio files; users usually record output manually.
Execution model
ÆTHRA renders audio offline (deterministic, no glitches).
Strudel runs in real time via the Web Audio API.
Use cases
ÆTHRA: game music, background scores, generative assets, scripting music like code.
Strudel: live coding, experimentation, performance.
Environment
ÆTHRA runs locally (currently Windows).
Strudel runs entirely in the browser.
Both tools are free, and they’re not trying to solve the same problem.
ÆTHRA is meant to feel closer to a music compiler, while Strudel feels closer to a live instrument.
ÆTHRA is early (v0.8), but it already supports tempo, ADSR, chords, scales, loops, echo/reverb, live preview, and WAV export. I will update AETHRA soon and make it very powerful to reach v1.0
Fair point. By “ethical” I’m referring to the intended and documented usage — authorized testing, education, and defensive simulations. Like any security tool, it can be misused, but Cyber+ is designed and presented around consent-based scenarios rather than real-world exploitation
By “ethical attack simulations,” I mean simulations intended for defensive security testing, education, and controlled lab environments (e.g. local machines, intentionally vulnerable targets, or systems you own or have permission to test). Cyber+ itself doesn’t try to enforce morality in code; instead, it focuses on transparency and explicitness so it’s clear what an action does. Like most security tooling, ethical use depends on authorization, scope, and intent rather than the language alone. I’m open to improving the wording if “ethical attack simulations” feels misleading or too vague.
Try Cyber+ out. I will be very happy if you'll help by giving me some syntax ideas.