News for hackers. Stuff that matters.
Re:Go: Ten years and climbing by kibwen on Friday September 22, 2017 @01:22AM (#15309583)
> I'm a much bigger proponent of languages such as Rust or Haskell which give the developer the _tools_ to ensure their own data integrity

As a big Rust proponent, I don't think it makes sense to invoke Rust here. The goal of Rust is to provide a more secure low-level foundation for software; any tools it provides to "ensure data integrity" are in service of that end, and pale in comparison to the sort of correctness that Haskell strives for on principle.

Given that Go is memory-safe (modulo a few concurrency foibles), any software that gets rewritten from C to Go is still a win in Rust's eyes. I know more than a few people in the Rust community who are big fans of both languages (e.g. burntsushi, author of Rust's regex library and ripgrep), and the Rust developers have a lot of respect for the Go authors. Go and Rust have different priorities, and that's A-OK.

Re:Go: Ten years and climbing by pjmlp on Friday September 22, 2017 @06:04AM (#15310634)
This is the main reason, why in spite of my complaints, I will support any Go project.

The end goal is that the overall software stack should become safer, regardless of what layers one is actually busy with.

Re:Go: Ten years and climbing by ngrilly on Friday September 22, 2017 @03:16AM (#15310029)
Kudos for this insightful comment on the respective merits of Go, Rust and Haskell.
Re:Go: Ten years and climbing by peoplewindow on Friday September 22, 2017 @12:28PM (#15313582)
I think the big concern is not so much rewrites from C to Go (more or less anything would be better than C), but the fact that there are other choices that'd likely lead to substantially better code which could have been taken but aren't.