To Solve This Problem Wyzer Introduces the Concept of Choreographic Programming Which Is One of the Few Serious Attempts to Solve It

Comments. Simplicity is not the absence of power. It is power without pretense.

~ Atiksh Sharma Feel free to use the prentensious quote anywhere lol. Wyzer is a statically typed, compiled, resource-oriented programming language with integrated distributed safety via choreographic programming and a perceus memory model Rust guarantees safety within a process It does nothing for: To solve this problem Wyzer introduces the concept of choreographic programming which is one of the few serious attempts to solve it. Contributions are welcome, if you want to contribute to the language please read RESEARCH.md Join our discord server as well:)) To learn how to program in Wyzer, check out our official documentation: Wyzer is designed to be simple, explicit, and easy to read.

Here is a quick look at how you write code in Wyzer. Everything has a clear type, and variables are immutable (cannot be changed) by default. If you want to change a variable, you must explicitly use var instead of let.

You can also use const for compile-time constants. You can define custom data structures and access their fields directly. Wyzer supports standard if / else, while, and for loops.

Note that loops don't need parentheses around the condition. Errors are not hidden. Functions that can fail return a Result.

You use match expressions to safely handle both the success ( Ok ) and error ( Err ) cases. Note that match is an expression, so if used as a standalone statement, it requires a trailing semicolon! A simple guide with no math.

Use this to explain the project quickly. Wyzer is a programming language built on one idea: most hard problems (like memory bugs, deadlocks, and network errors) happen because it is not clear who owns a resource. Instead of using three different tools to fix memory, concurrency, and networks, Wyzer uses just one ownership rule for all three.

This is a fair question, and the honest answer starts with what is already good about existing options, not what is wrong with them. Rust proved you can have safe memory without a garbage collector. This is great, but Rust is hard to learn, and its rules make some common code structures difficult to write.

Go, Java, C#, and Python use garbage collectors. This makes them easier to use but slower and less predictable. This is bad for real-time or low-level systems.

Network programming is still mostly done by hand. You write two programs and hope they talk to each other correctly. When they don't, you get bugs.

Wyzer's goal: Get the safety of Rust without the difficulty, and use the same rule to make network programs safe too. Most of Wyzer's pieces already exist. What is new is putting them together.

The benefit: You only need to learn one rule to manage memory, threads, and networks safely. These are the values that drive our decisions. They explain why Wyzer looks the way it does.

One way to write a thing. If there are two ways to write the same thing, we remove one. No hidden magic, but keep it clean.

Important things should be visible in the code, but you shouldn't have to write extra boilerplate. Let the compiler do the work, unless it is confusing. We want the compiler to figure things out, but we require clear rules when things get tricky.

Be honest about what is not finished. We mark unsolved problems clearly so people know what needs work. This section is a simple map of the formal rules.

Read this first to understand the basics. Memory (Section 5): You write functional code that does not change data. Behind the scenes, if a piece of data has only one owner, the compiler changes it directly in memory.

This makes it as fast as C without a garbage collector or lifetime rules. Ownership is everything (Sections 3, 6, 7): The one rule is that once you use a resource, you cannot use it again. This applies to memory, network messages, and hardware interrupts.