Lies we tell ourselves to keep using Golang

Re:Lies we tell ourselves to keep using Golang by andai on Friday April 29, 2022 @07:00PM (#31211591)

I was struck by ThePrimeagen[0] saying that it took him 5x longer to write a game server in Rust than in Go—despite having significantly more Rust experience. They performed about the same (I think Go actually did better due to how much easier it was to get concurrency working?).

Personally I lean towards strict compilers (I suppose years of JavaScript has traumatized me), but 5x dev time is a big tradeoff! Of course this is just one data point, but it did seem worth mentioning.

[0] - https://www.youtube.com/watch?v=Z0GX2mTUtfo

[ Parent | on HN ]

Re:Lies we tell ourselves to keep using Golang by ay on Friday April 29, 2022 @07:35PM (#31211830)

My experience in writing a small side project in both (on the order of 2-3 KLOC) was that the time to a working project is significantly shorter with golang. The time to the correctly working project was about the same between the two.

Golang gets out of the way in me doing what I want.

Rust actively resists me doing things I will later regret.

Also, unexpectedly, I have gotten some positive comments on my C coding style after I coded some Rust.

All of this is completely anecdotal and personal experience, of course.

[ Parent | on HN ]

Re:Lies we tell ourselves to keep using Golang by lupire on Saturday April 30, 2022 @03:36PM (#31218603)

99% of people don't need "correctly" working projects.

Trillion dollar companies run on "incorrect" software.

[ Parent | on HN ]

Re:Lies we tell ourselves to keep using Golang by warabe on Saturday April 30, 2022 @06:40PM (#31220148)

Then, it's time to move on.

It is impossible to run "correct" software, but we can do better, maybe?

[ Parent | on HN ]