1. Documentation & examples are missing
"your README and docs don’t describe any of the interesting or unique things here. You cover
ifin README but not choreographic programming or perceus. Did i miss some big link?" — jitl
"There’s not a single example." — andai
"You should lead with a concrete choreography example before any syntax details." — jerf
2. Skepticism about theoretical claims (deadlock, memory safety)
"How you can guarantee the lack of a distributed deadlock? … What stops a choreography where Claire sends to Bob but Bob is waiting for Alice?" — snek_case
"What’s the plan for cycles with ref‑counting? … a cycle collector, weak refs, or just accept the leak?" — minraws
3. Rust‑like syntax is appealing, but the core innovation needs clearer exposition
"The syntax is very generic and conservative. I’m extremely positive about that." — hyperhello
"I love the ambition and the fact that this is not just another ‘state of the art in 2015’ language." — jerf
Overall, the community wants front‑loaded, concrete examples of choreography and a transparent discussion of safety guarantees, while praising the Rust‑inspired syntax but urging the team to highlight the unique value up front.