Wyzer - Safe systems programming with one ownership rule
Show HN: Wyzer Programming Language
Wyzer is a statically typed, compiled programming language that unifies memory, thread, and network safety through a single ownership rule. It combines Perceus reference counting for fast memory management without a garbage collector, and choreographic programming to automatically generate correct network code, preventing deadlocks and protocol mismatches. Designed to be simpler than Rust while offering similar safety guarantees, Wyzer is ideal for developers building reliable distributed systems. Its syntax is clean and explicit, with immutable-by-default variables and clear error handling via Result types. Explore the documentation and start coding in Wyzer today.
One ownership rule for memory, threads, and networks. No garbage collector, no complex borrow checker, and no network errors.
- jerf
I love the ambition and the fact that this is not just another "state of the art in 2015" language like I see so often. It's trying to do something genuinely different. The field of "taking stuff out of academia and making it work" is a rich and underharvested one.
However, your light is hidden under a basket, to use an old metaphor. I'm having to go digging to find the genuinely new things going on. I suggest recalibrating the entire documentation with a focus on the new stuff. People on HN often complain about not having syntax examples front and center but I would say for you, the very first thing I you should be hitting your new visitors with is the choreography idea.
Set up a simple example of doing something like a concurrent remote counter that is atomically safe by the construction of your language and immediately dive in to what that means. Forget even educating us on the rest of the mundane syntax of the language, immediately dive in to what that is and what that means. I see in the docs/ dir that it probably hurts your programmer mind to cover the choreography before covering sections 1-8, but you can safely assume that if you intrigue with the choreography that they'll hang around to learn about the rest, whereas you can't safely assume that a new reader will wade through all the rest of the relatively mundane details to get to the really interesting stuff.
A modern language with a modern take on compiling a "program" that takes a unified view of the world at the […]
- hyperhello
First of all, the syntax is very generic and conservative. I’m extremely positive about that. It just looks like C or Typescript or Java to me and I don’t see mysterious diacritical marks.
The next thing is, I need more examples. Read me documents can scroll forever and that’s fine. Add examples for every concept your language wants to cover to it. This is your chance to think things through and make the read me and the language astonishing.
And your AI disclaimer (or your AI’s disclaimer) makes sense.
- vlovich123
One thing I don’t understand is how you can guarantee the lack of a distributed deadlock. I’m sure it’s covered in the underlying research, but just conceptually it’s hard to picture.
What stops a choreography where Claire send a message to Bob but Bob is waiting for Alice and Alice is waiting for Claire?
Is it like Rust memory safety where not all valid programs are accepted but all invalid programs are rejected?
I think some examples of the distributed code in action on a trivial and non trivial distributed example is more compelling than a 3d donut render
- jitl
Your README and docs don’t describe any of the interesting or unique things here. You cover `if` in README but not choreographic programming or perceus. Did i miss some big link?
Where’s the cool stuff?
- gwbas1c
I really appreciate this:
> 1. What Wyzer Is, In One Paragraph...
> 2. Why Make a New Language At All?...
Far too often I see projects on HN where, on a casual skim, I just can't figure out "the point." This is clear and concise.
---
One of the issues with "Writing one network rule that creates code for every computer. We borrowed this from academic research" is that often it's hard to have the same language on every computer. For example, for a web application, you're either going to have to transpile to Javascript or target WASM. (And WASM has a lot of overhead compared to Javascript.)
- renox
Congratulations your language is trying to solve an hard problem.
But .. your language mostly hide when you're doing an 'inside' function call or an 'external' function call.
I'm not sure I like this;
1) the latency of both operation is very different so you want to minimise the number of 'external' function calls
2) what happens in case of 'timeout' for external function calls?
I didn't see it in the doc, did I miss it?
- hmokiguess
I saw this medium post from you https://medium.com/@atixwasfound/how-i-began-writing-my-own-...
In there it says you started this journey when you were 8 years old and that you are a 14 year old programmer
I'm not sure how I feel about this to be honest, I need to process that.
- nicoburns
Huh, the Choreographic Programming (https://github.com/Wyzer-Lang/wyzer/blob/master/docs/08_chor...) looks very like "server functions" as implemented in Next.js / Dioxus / Leptos, but generalized as a language feature.
Definitely a cool idea. I guess time will tell whether lifting it into the language proves itself as worth it.