[rcxdude]

Hmmm, given the general mood in this case, I feel like there's a lot of people keen to find any criticism of the code they can and amplify it as possible. Most of it strikes me as relatively shallow at the moment, though (that is, apart from the fact that merging such a large LLM assisted port is certainly a, uh _bold_ move (to put it lightly), there's not much that people are pointing out about the actual result that feels like it's worse than any other port in progress, but there is definitely a lot of hay being made about any issue that is found).

[antonvs]

> Most of it strikes me as relatively shallow at the moment

It is. We’re what, a week into this exercise? Absolutely everyone criticizing it, with no exceptions, is behaving like a micromanaging middle manager who couldn’t even dream of doing the work themselves.

I half want to start a list of “people to ignore”, but such people tend to expose themselves in every other comment anyway.

[rajup]

Idk the pr author did merge it into main and talked about writing a blog post. To me that sounds like the author felt it was ready for public critique and feedback, especially for software with a fair bit of users

[antonvs]

It's not replacing the stable build, and not being claimed as bug-free. "Public critique and feedback" is not meaningful or useful if it just consists of regurgitating what's happening in a more negative and uninformed way.

[stickfigure]

It may just be different expectations about what the `main` branch means. In my organization we don't merge half-finished work into `main`.

[antonvs]

This isn't replacing the Zig stable build at the moment - it would make no sense if it was. It's not unusual to merge separate non-prod functionality to main once something is ready for others to work on.

And realistically, essentially 100% of the people criticizing this don't have the the credentials to do so meaningfully.