... or (maybe) incus.

it's what I'm deploying everything on right now... it's still early and the update restarts everything... eeek.

After GIL they must add Result/Option and drop exceptions.

In Python, exceptions are effectively free, unlike JVM or .NET. Every for loop in Python relies on those exceptions.

Can uv replace a `pipx --global` install option?

Is this another attempt to make a tool like a rust's cargo for c++?

try pyoxidizer

What about NVME optimizations?

How long did it take to develop each web service? Which rps produces?

In terms of RPS, this web service is more-or-less the fortunes benchmark in the techempower benchmarks, once the data hits the cache: https://www.techempower.com/benchmarks/#section=data-r21

Or, at least, they would be after applying optimizations to them.

In short, both of these would serve more rps than you will likely ever need on even the lowest end virtual machines. The underlying API provider will probably cut you off from querying them before you run out of RPS.

Author here. It took me about 2 hours to code the Go service and maybe 4 to do the Rust part. The reason why Rust took longer was mainly because of the better error handling and the few more higher level abstractions. I could have added unwraps everywhere to get about the same experience, but yeah.

Honest question: how does "better error handling" cause the implementation time to increase?

Better error handling in the final result.

It's a pizdezh.

I try this release on debian buster:

nvim: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by nvim)

Why binary doesn't support old glibc?

You can probably get this version of Neovim to run on your Buster system with Nix, which will pull in a newer glibc in an isolated/self-contained way if its Neovim build needs it!

I left some instructions for how to get started with this in this comment, if you're interested: https://news.ycombinator.com/item?id=35482673