do_not_redeem

> Pure-Go tree-sitter runtime — no CGo, no C toolchain, WASM-ready.

No you didn't. The readme is obvious LLM slop. Em-dash, rule of three, "not x, y". Why should anyone spend effort reading something you couldn't be bothered to write? Why did you post it to HN from a burner account?

Zig supports this. If you compile with -fsingle-threaded, operations on mutexes turn into nops, atomics become simple loads/stores, etc.

Okay, let's say the cache is cold and you're on an old clunky spinning rust 5400 RPM hard drive. Do the math. How long will it take, worst case, for the platter to spin to where calc.exe is stored?

I won't spoil the article, but if you read to the end you'll find out what this "FMZ" project is called.

It was an offhand 20 words out of a 5000 word article and a very pertinent example. I guess the question is, why were you not bothered by the negative opinion about instant coffee or particleboard or malls or Tinder or McNuggets, but hearing anything negative about LLMs is worth singling out to complain about?

To be fair, Windows 8 only came out in 2012, so they haven't had that much time to finish the settings migration. But they're making good progress. If they keep up this pace of moving 2 settings per month, they should be able to finish by 2053.

I wonder what tools the Zig team has to deal with trolls like this.

Is the zig name or logo trademarked? What about the mascot he's using as his github picture?

They're violating the terms of the MIT license as mentioned in the article, so maybe Zigtools has legal standing.

As for lying about no AI, being an asshole isn't illegal, so no angle there.

Any other ideas I missed?

Congratulations on the move!

> Thank you to the Forgejo contributors who helped us with our issues switching to the platform, as well as the Codeberg folks who worked with us on the migration

I'd love to see a writeup about these problems/solutions at some point.

I think gorhill is far more trustworthy than a whole new browser based on crypto.

Reading between the lines, it seems like Google is playing a bit of chess here. Reminds me of the Beeper Mini stunt, except this time by a trillion-dollar company they can't just sweep under the rug.

> we welcome the opportunity to work with Apple to enable “Contacts Only” mode in the future.

> I applaud the effort to open more secure information sharing between platforms and encourage Google and Apple to work together more on this.

Your move, Apple.

> I can send multiple queries over a single TCP connection and receive multiple responses over the same single TCP single connection, out of order. No blocking.

You're missing the point. You have one TCP connection, and the sever sends you response1 and then response2. Now if response1 gets lost or delayed due to network conditions, you must wait for response1 to be retransmitted before you can read response2. That is blocking, no way around it. It has nothing to do with advertising(?), and the other protocols mentioned don't have this drawback.

yt-dlp + 4K works fine for me. The only special thing I remember doing is adding the impersonate feature (which it prompts you to do if it needs it). In other words, instead of `uv tool install yt-dlp`, run `uv tool install yt-dlp[default,curl-cffi]`

The version in the Arch repos does not include the impersonate feature.