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 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 ]