https://www.memorysafety.org/blog/introducing-river/

It's mentioned briefly in the Cloudflare blog post. I'd expect that if you're a current nginx or other proxy, River is what you'd want as an alternative.

One of the big things I'm excited about in the River plan is the ability to use wasm for scripting, which should make it relatively easy to extend.

Or if you run shared hosting or some other scenario where you are effectively maintaining your server configuration twice: once for the actual server and once in the database for your dashboard and other services. This would allow you to just read the config from the canonical source, instead of risking bugs when the two configs diverge.

- Security is your top priority: Pingora is a more memory safe alternative for services that are written in C/C++.

- Your service is performance-sensitive: Pingora is fast and efficient.

- Your service requires extensive customization: The APIs Pingora proxy framework provides are highly programmable.

So that'll certainly one option in the future.

That side of the connection usually isn't going over slow and lossy mobile networks, so QUIC isn't that useful there.

https://github.com/cloudflare/pingora/blob/main/docs/quick_s...

Its an indigenous word, but probably not the indigenous name for the mountain. I've heard it means "high, rocky and inaccessible peak" in Shoshoni. Popo Agie (pronounced puh-poe-zha) Tower was proposed, but there are dozens of Popo Agie things already (the Popo Agie river runs from the Wind River range, through Sinks Canyon into nearby Lander, Wyoming), so the USGS insisted on a more distinct name.

The switch to Rust has been very positive overall, because it allowed Cloudflare to tackle much more ambitious projects, and own its entire stack.

it might be needless, but for those of us not in the know, could you elaborate on that please? what ended up as waste? why? altogether was it worth it?