News for hackers. Stuff that matters.
[dead]
Re:MemGuard: Secure sensitive information in memory in Go by paulfurtado on Friday July 26, 2019 @05:02AM (#20533385)
In this case, this is a library for Go, not a standalone program, so it seems worthwhile to include the language in the description. If there's something technical about Go that makes pure-go implementations of things interesting it's that it's uncommon/frowned upon to use cgo to import c dependencies whereas in python/ruby/etc you can trivially wrap a C library for many things and call it a day.

Also, you mention you don't see similar posts for other languages, however, similar complaints are constantly lodged against Rust posts, maybe even more so than Go. A recent comment in one of those threads also mentioned similar musings were common against python earlier in its history.

Regardless, Go and Rust are popular languages on HN right now because they're new and interesting and being used to build interesting new software. In practice, other older languages are more popular for work, but as the library ecosystems improve, maybe that will change or maybe it won't.

Re:MemGuard: Secure sensitive information in memory in Go by nirui on Friday July 26, 2019 @07:57AM (#20534069)
Yeah I kind know what you mean, but this kind of expression (Very similar to Whataboutism) is how flame war started.
Re:MemGuard: Secure sensitive information in memory in Go by hu3 on Friday July 26, 2019 @07:02AM (#20533861)
I recalled seeing a flagged comment by this account in another Go thread. Took a minute to find it:

> For me, the best way to optimize a Go program is to write it in Rust.

That, along with other anti-Go comments, explains things.

Re:MemGuard: Secure sensitive information in memory in Go by innocentoldguy on Friday July 26, 2019 @02:22PM (#20537089)
They explain that I dislike Go. I thought my comments on it made that clear. I think Go is a half-baked throw-back language that handles threading, errors, and dependencies poorly, and is restrictive and lacks features. If Google hadn’t invented it, I doubt it would have any sort of following at all.
Re:MemGuard: Secure sensitive information in memory in Go by pjmlp on Friday July 26, 2019 @06:35AM (#20533756)
You weren't paying attention.

Plus the written in C, Pascal, C++, Modula-2, Java... was taking place on BBS, USENET and written media, so hardly easy to find on HN.

Re:MemGuard: Secure sensitive information in memory in Go by elp on Friday July 26, 2019 @07:17AM (#20533896)
So much this.

I remember how rabbid the python, perl and php fan boys all were back in the early days of their existence and how irritating they were to every one else.

I think its a sign of a language with a growing user base, and I suspect is that languages that don't generate this kind of fan base die off much earlier on.

Re:MemGuard: Secure sensitive information in memory in Go by innocentoldguy on Friday July 26, 2019 @02:24PM (#20537099)
I’m specifically talking about HN and the modern day. I found Perl fanboyism annoying as hell on Usenet back in the day.