[PussyLang] A minimal scripting language with bytecode VM and AOT C backend!

[u/Solid_Statement6313]

Hi everyone,

I've been working on a language called PussyLang (yes, funny). It started small but grew into something I'd like to share and get feedback on.

What it is

Dynamically typed, imperative, C‑like syntax. Compiles to bytecode that runs on a custom Java VM. Also supports ahead‑of‑time compilation to native executables by transpiling the bytecode to C and compiling with gcc.

func factorial(n) {
    if (n <= 1) return 1;
    return n * factorial(n - 1);
}
print factorial(5);

var arr = [10, "hello", true];
arr[1] = "world";
print arr[0];

Expandability and Customization

One thing I'm proud of is how easy it is to extend or modify PussyLang. I built it with the idea that users (or myself) might want to add new native functions, change the syntax, or even replace parts of the compilation pipeline.

• Adding native functions: In the Java VM, you just implement a class that implements NativeFunction and register it in NativeRegistry.registerAll(). In the C AOT backend, you add a function with a Value signature and an entry in native_table.
• Changing the bytecode or VM: The compiler, VM, and bytecode format are decoupled. You can add new OpCode values and implement them in both Java and C without breaking existing code.
• Lexer/parser: The lexer and parser are short. Adding a new keyword or operator is straightforward.

The whole thing is MIT licensed fork it, change it, use it in your own projects.

I made it this way because I wanted a language that could evolve with who uses it. If someone wants to add a for loop or a new built‑in networking protocol, they can do it.

What I'd Like Feedback On

1. The type system — only number, bool, string, array, bytes, function, null. Is that enough for most scripting tasks?
2. The C AOT backend — it's a lot of extra code. Worth maintaining? Or just stick with the Java VM?
3. Any obvious missing features that would make the language more practical without bloating it?

Links

• GitHub: https://github.com/Mynuramy/PussyLang

[u/yorickpeterse]

As stupid as I think the name may be, we don't have any rules regarding project names (IIRC this is the first time in years there's a project with a dubious name) so I'll give it a pass.

[u/Solid_Statement6313 → u/yorickpeterse]

thanks <3

[u/HeraclitusZ → u/yorickpeterse]

I am disappointed with this decision and think you should reconsider. The name of this language *paired with the logo in the repo* leaves no doubt that this is name is a sexual reference, which should be against rule 2. The programming language community already has enough issues with exclusionary practices, and I don’t think we should be bending the rules to *regress* and make it more of a boys club here.

[u/Solid_Statement6313 → u/HeraclitusZ]

I don't think is that deep for small hobby project that grew a bit over time + this isn't regressing anything (I am a women),the name started kinda of an inside joke between me and friends, the language itself if you look into it has nothing sexual, but thanks for criticism .

[u/yorickpeterse → u/HeraclitusZ]

The logo wasn't there when I first wrote the comment, as it was only added about 3 hours ago. It's indeed not what I would exactly consider classy, so I'll flag the post as NSFW.

As for /u/Solid_Statement6313: please keep your future submissions more mature.

[u/Solid_Statement6313 → u/yorickpeterse]

Yeah mybad! I will thanks for opportunity to share it anyways!

[u/Ifeee001 → u/HeraclitusZ]

The programming language community already has enough issues with exclusionary practices, and I don’t think we should be bending the rules to regress and make it more of a boys club here.

Just curious, what exclusionary practices are you talking about? And what in the subreddit/subreddit posts makes it a "boy club"? Obviously excluding the current context