Go has shorter and more predictable GC pauses. If a reference count drops to zero in Rust, it may take an unbounded time to free all the things it refers to (recursively if necessary).

The datetime to string conversions in Go are devil's spawn.

Go has warts, but projects like Lisette (https://lisette.run/) try to fix those. Go has bare syntax, as lack some (modern?) features. But imho it has a superb runtime, eg has a WAY better concurrency story than what you see in Rust.

I never feel rust learning curve is steep. It is just everything is awkward, even more awkward than modern C++.

Some years ago Go was all the hype rage.

Now Rust is the new Go.

I find that very confusing.

What about AI assisted migration?

There was a signal to assist c++ to plain and simple C AI mass migration.

Removing any languages with ultra-complex syntax towards simple and plain C is always a good thing.

I

JVM languages to Rust, I understand it somehow.

But Go to Rust???

It does not make any sense.

> Under heavy allocation, P99 latency tails are noticeably worse than a Rust equivalent that simply doesn’t allocate on the hot path.

Lmao so not an equivalent then? Standard glibc malloc, which is default in rust, will also similarly degrade albeit for different reasons.