Performance metrics generally put Rust squarely ahead of Go, but not by a lot.

10x, 4x and 3x performance difference is not "but not by a lot", it is al lot! :D Imagine needing 1 server vs 10 servers to run same app. Same for memory.

Can people stop contradicting themselves when comparing X with Rust just to make X look less horrible, please!

Nop nop nop! If I ever make a single API in Rist ever again I’m gonna go to the last apartment’s floor, break the door for the roof, get a power cable from one of the solar panels installed there, tie it up to the door handle and then run and jump so I have a less painful death than writing a Rust “microservice”.

Rust is beautiful language. In its own weird way. But not for multithreading async communication. Let’s not start talking about tokio and async-std and their controversies and the language hasn’t figured out yet a standard way to do async. And definitely not for connecting to databases or other standard things you do very easily in Go or NodeJS, especially in Go where you have Goroutines and really easy to read and write maintainable code. Last time I wanted to connect to a database in Rust for a microservice I was doing 100 times more leaning the “ecosystem” of Postgres in rust or MongoDB, and I still didn’t manage to do it and so I thought wait a minute, every single time I’ll have to figure or someone else these shits out? Fuck it, back to Go.

I’ll do other things in Rust. Like pure system programming. Just …….. not web services.