Top
Best
New

Posted by v0id_isgood 19 hours ago

Show HN: Wyzer Programming Language(github.com)
So i've been working on this project since a few days (or months i should say), it's called wyzer (meaning wiser) it's a statically typed, compiled, resource-oriented programming language with integrated distributed safety via choreographic programming and perceus memory model, The reason why i began this project is out of frustration from Rust, you see it does provide safety for your memory by the strict type checking but what it does not gurantee safety against are distributed deadlocks which is basically a few independent nodes or services wait permanently for resources or messages held by each other, forming a circular wait, the rest are cross-service correctness and protocol mismatch as well. If we are specific over here Wyzer works on mainly generalizing the concept of choreographic programming in a high level programming language because its the very few attempts of actually solving these gaps of safety. Instead of borrow checkers and lifetimes wyzer has linear/affine types and a perceus reference counting which is computationally much simpler for an LSP to understand as well

after 5 months of research and a few weeks of development i am soon going to release version 0.1.0 of it, if you would like to contribute to it you're most welcome!

188 points | 105 commentspage 4
taolson 14 hours ago|
Since your language is very "rust-like", what made you choose Ocaml as the implementation language?
v0id_isgood 14 hours ago|
Ocaml was very simple to program in to be honest, and has very minimal rules as well so i can be productive with the development of the language, Rust also used ocaml in it's early versions for bootstrapping
manithree 17 hours ago||
docs.wyzer-lang.org doesn't resolve for me, and it's prominently linked from https://wyzer-lang.vercel.app/. Since I'm not familiar with wyzer or perceus, how would one write, say, a doubly linked list in wyzer?
v0id_isgood 16 hours ago|
docs are under development, you can check them out soon :)
thomasmg 16 hours ago|||
Great. I'm also writing a new language with the same memory management idea (Perceus-style reference counting / ownership). My language [1] is not functional and currently lacks multi-threading and networking, so there are big differences. But I really like the moto "easy to use memory safety without tracing GC".

[1] https://github.com/thomasmueller/bau-lang/tree/main

jitl 16 hours ago|||
maybe wait until you have something to share before Show HN? overall your work seems like a cool thing that i’d like to look at in a few months once there’s more substantial education stuff to read about it.
DauntingPear7 13 hours ago||
The website on mobile is basically unusable. I like the general theme though
pjmlp 16 hours ago||
No mention of the much more mature Chapel, with industry support, given the domain?
Myzel394 15 hours ago||
Looks promising, let's see into what this evolves
nirbendavid 15 hours ago||
i wonder how agents would adopt a whole new programming language, as not much syntax examples / references are out there.
bramadityaw 13 hours ago||
question: how accurate is the intuition that role types are the location a computation happens?
mring33621 14 hours ago||
I love the website!
REDA_MAH 16 hours ago||
The syntax is soooo promising but still we need more documentation. Good job anyway for doing such an amazing work with no ai
phplovesong 15 hours ago|
Ref counting IS a form of GC. It can be slow and have issues in high perf scenarios.
More comments...