Wyzer

Languages and libraries

programming language

SHOW HN2026

227points
120comments
#230of 4,366 in 2026
Top 6%of 2026 by points

How HN took it

MixedNo clear lean

10 positive, 32 neutral or asking, 4 mixed, 24 critical, out of 70 comments about the project. Thread score -0.15.

Docs: 5 for, 10 againstIdea: 2 for, 3 againstDesign: 2 for, 3 againstPerformance: 0 for, 2 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Novel focus on choreographic programming

    From 2 comments
    • 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…
      jerf on HN
    • I like the ideas a lot. The Readme needs some polish (I think it’s great that it reads as hand-written; an LLM could make suggestions that make it just 10% easier to read). Is…
      bckr on HN
  • Clean, conservative syntax

    From 1 comment
    • 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…
      hyperhello on HN

Objections

  • Documentation does not explain choreography or show examples

    From 3 comments
    • 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?…
      jitl on HN
    • I skimmed so I may have missed it, but nowhere in the README do I actually see a description of what "choreographic programming" is, or an example of it.
      adastra22 on HN
    • The tests I could find for ‘choreographed programming’ were 1-2 lines long and demonstrated absolutely nothing, certainly nothing as elaborate as the research text is stating.…
      dwroberts on HN
  • Perceus with linear resource rule seems contradictory; cycles may leak

    From 1 comment
    • The pitch is "one ownership rule for memory, threads, and networks," but I think there are two rules in here and they pull against each other. The resource rule as stated is…
      imthenitto on HN
  • Timeout and external call handling unclear

    From 1 comment
    • 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…
      renox on HN

Requests

  • Add concrete code examples

    From 3 comments
    • 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…
      hyperhello on HN
    • Very interesting. Maybe this would benefit from concrete examples, of things that are difficult or impossible in other languages, but well supported in Wyzer? I see there's a few…
      andai on HN
    • nice Rust-inspired syntax, although if the main selling point is choreography here, that isn't featured enough on web page or README. Needs more examples/explanation of how that…
      netniuq on HN
  • Explain how choreographic programming works

    From 2 comments
    • For anyone looking for an easily digestible primer on choreographies: https://decomposition.al/zines/communicating-chorrectly-zine.pdf Too bad the github readme doesn't explain…
      rbr94 on HN
    • As someone working on a language in this space, I think your README could be much better. Most of the important stuff is in this section: ```3. What's Actually New About It?```…
      onlyrealcuzzo on HN

Questions

  • How are distributed deadlocks prevented

    From 1 comment
    • 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…
      vlovich123 on HN
  • How does Perceus handle shared data and performance

    From 1 comment
    • > 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.…
      whateverboat on HN

Alternatives named

  • Rust

    From 1 comment
    • As someone working on a language in this space, I think your README could be much better. Most of the important stuff is in this section: ```3. What's Actually New About It?```…
      onlyrealcuzzo on HN
  • Chapel

    From 1 comment
    • No mention of the much more mature Chapel, with industry support, given the domain?
      pjmlp on HN
  • Session types

    From 1 comment
    • I like the ideas a lot. The Readme needs some polish (I think it’s great that it reads as hand-written; an LLM could make suggestions that make it just 10% easier to read). Is…
      bckr on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/49209385)