Hacker Newsnew | past | comments | ask | show | jobs | submit | v0id_isgood's commentslogin

cool project!


I hope you liked wyzer :)


i heard you guys and took my time to improve the project with the feedback which i really appreciate, i really don't know how to delete this HN since someone impersonated me from this account which really isn't mine. You might have expected a polished language and found a WIP programming language which i'm really sorry for, i updated the README as per the people's request and also got the documentations up on the website! :) , i'm open to more feedback and assistance to make the project better and most importantly questions! (i do have to really fix the documentation but i'd rather focus on the language first)


examples aren't updated yet some guy who mocked me earlier for the language on discord deleted his statements and walked away blocking me after giving me his hacker news credentials, now here i am answering to your questions


wait what? You're joking. Some rando just picked a fight, walked it back, then gave you his HN account?


sounds fake but it's true, i am still confused till this date, but he actually didn't really do me a favour since he basically made an HN post when the language is basically not even in beta and to be honest , there's a saying "first impression is the last impression" so he just really destroyed the reputation of the project and told me to handle the gigantic crowd


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


open an issue we can discuss about it there :D


if you think so then open an issue or contribute to it :D we can discuss about it and decide which is the best option


This is hands down some of the most constructive feedback we’ve received. You hit the nail on the head.

We definitely fell into the author’s trap of structuring docs "bottom-up" (Prerequisites -> Basic Syntax -> Advanced Concepts) rather than leading with our actual core innovation: choreography.

We are restructuring the main README/docs front page right now to lead immediately with a concrete example of choreographic execution (e.g., atomic multi-node orchestration / client-server emitting) before getting into standard syntax.

Really appreciate you taking the time to dig into the docs/ dir to pull this out it’s a huge help for our presentation.


You should avoid LLMs in your communications.


You do realize its not the real creator right? Its someone impersonating.


It’s the OP who posted the link.


Yes, but the OP is not the creator, which he claims to be. You can see the discussion about it on the discord server of Wyzer. This guy made all of this post, then left the account credentials to the real creator a few hours ago.


You should still keep doing the bottom-up approach for the rest of the docs. Just update the README first paragraph or two as the gp says.


Yes, strong agree, normalcy resumes at some point. But you want the hook in first.

I mean, I'm phrasing that in marketing terms, but in this case it's in harmony with what your users want anyhow. We want to know ASAP why we should care about this language. So it works for everyone. Of course when it comes time to deliver the promise, normal programming language documentation is the way it is for a reason.


you should really put some of the content in RESEARCH.md to the README.md. The language's core idea shouldn't just be known to contributors.


> linear/affine types and a perceus reference counting

You should put these up front also.


Lmfao.

This is not an LLM talking but a kid who is learning to write with them, if you look closely. Still concerning


I think it's quite rude to reply to a well thought out comment with AI slop


The OP is not the creator of wyzer. Its someone impersonating. You can see the discussion about it in the discord.


author is 12 year old. future kids are AI native i guess


this REALLY reads like claude responded to this comment, so I really hope that I'm just mistaken and you just naturally talk like this


const can be used in places that need a compile-time-known value (like a fixed array size). let can't, even if it obviously holds a fixed number.


isn't there a way to infer that from context? like if the variable is declared with the Comptime role. Some guy said that the const keyword was a mistake C made that is then blindly followed by its successors.


time flies :) the grass was greener before though and i miss that!


Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: