Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I also like dart having used it for flutter.

How’s the performance story when using for backend?

I love and use go for 99% backend and node for scripts (usually there’s a npm package that does what I need - done in 10 min) or spinning up simple aws lambda.

Go is so highly performant at all things including CPU bound tasks (no point comparing io bound stuff, although it can handle a larger volume of these).

Plus the scaling story is that it just always works fast the more resource you throw at it.

I don’t use rust because I don’t need that level of perf. If rust is 10 go is 8-9. That’s fine for me. For context I have services doing 10-100k rps that cost me like $4 plus bandwidth (depending on usefase, each).I don’t need beefy instances.



I mean it’s a fully compiled, optimized machine code binary that I deploy but having said that, it’s not Rust or Go and I wouldn’t expect 100k rps at all.

I just throw it up on Cloud Run and let it auto scale up and down as required and call it a day.


Stop putting Go in the same bucket as Rust. You never looked at its low-level details. Please do.

It has weak compiler, expensive write barriers and neither offers you APIs to reach optimal hardware utilization (aside from completely custom ASM dialect) nor the ability to define zero-cost abstractions.

Its purpose is fast networked back-end applications that are scaled horizontally (by cranking replica count, because Go's GC does not scale well with cores, and the CSP pattern has scalability issues too), but that's pretty much it.


I’m literally responding to someone who talked about Go and Rust who wanted a comparison.


Interesting. Thank you!

Cheers




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: