News for hackers. Stuff that matters.

A comment on Taming Go’s memory usage, or how we avoided rewriting our client in Rust. Parent comment

Re:Taming Go’s memory usage, or how we avoided rewriting our... by throwaway894345 on Tuesday September 21, 2021 @04:48PM (#28609730)
I assume it's tongue-in-cheek; because "rewrite in Rust to improve performance" is such a meme, the headline is subtly calling attention to the fact that this is rarely good advice and certainly not the first lever an engineer should reach for upon running into a performance problem.
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by maleldil on Tuesday September 21, 2021 @04:56PM (#28609828)
> subtly calling attention

That's generous. I'd call it clickbait.

[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by wibagusto on Tuesday September 21, 2021 @06:06PM (#28610608)
Well consider all the projects titled “blah blah blah… written in Rust”

Who gives a shit what it’s written in—what does it do?

[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by marcos100 on Tuesday September 21, 2021 @06:51PM (#28611016)
People who is interested in rust maybe want to see how it was used.

The author could have just kept "Taming Go's Memory Usage".

Maybe they never considered rewriting in rust. The pros and cons looks like just some random arguments to add rust to the title.

[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by pm90 on Tuesday September 21, 2021 @07:57PM (#28611537)
> The author could have just kept "Taming Go's Memory Usage".

It’s their article. They can choose to write it however they want. You may find this type of humor distasteful, fine, write your articles that way.

As a user of both rust and golang, I chuckled at the headline and then forgot about it.

[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by gobookdev on Tuesday September 21, 2021 @08:17PM (#28611685)
a
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by throwaway894345 on Tuesday September 21, 2021 @09:27PM (#28612159)
TFA doesn’t argue that one is better than the other? Maybe you’re commenting on unrelated “click bait shit”?
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by brundolf on Tuesday September 21, 2021 @04:55PM (#28609816)
It's not the first lever an engineer should reach for regardless of the languages involved. Calling out Rust specifically feels like a bit of a cheap shot
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by pjmlp on Tuesday September 21, 2021 @05:02PM (#28609906)
To be fair, that is now the common "I rewrote X in Y" theme, which followed upon the Y ∈ { Ruby, Clojure, Scala, Kotlin,.... } from previous years.
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by Zababa on Tuesday September 21, 2021 @05:39PM (#28610336)
And Go too! It's always fun to see posts from around 2014/2015 complaining about how every submission to Hacker News is now "I wrote X in Go", while now Go is the boring stuff and Rust is the hot new thing. I wonder what will be the next Rust though.
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by tptacek on Tuesday September 21, 2021 @05:42PM (#28610378)
BPF-verified C.
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by SAI_Peregrinus on Tuesday September 21, 2021 @10:27PM (#28612518)
Naw, BPF-verified BF. Or someone will make "BrainFuck Plus" so we can get BPF-verified BFP.
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by pjmlp on Tuesday September 21, 2021 @06:20PM (#28610745)
Some GC based language with dependent types.
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by square_usual on Tuesday September 21, 2021 @09:10PM (#28612045)
Nim is on the way up in HN posts...
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by Zababa on Wednesday September 22, 2021 @02:40PM (#28620056)
Nim has dependent types?
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by klyrs on Tuesday September 21, 2021 @10:25PM (#28612504)
Write it in Malbolge? Slightly less silly, modern C++ and modern Python are evergreen.
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by Zababa on Wednesday September 22, 2021 @04:44PM (#28621537)
They are, but they also are too big, so at some point people will want to replace them with something simpler/smaller. Go has been used for this for some projects in C++ and Python.
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by throwaway894345 on Tuesday September 21, 2021 @05:05PM (#28609947)
It's a shot at the "just rewrite it in Rust" meme, not at Rust or the Rust community.
[ Parent | on HN ]