News for hackers. Stuff that matters.
Re:Rustgo: Calling Rust from Go with near-zero overhead by kmicklas on Wednesday August 16, 2017 @05:32PM (#15031559)
> Share memory by communicating, don't communicate by sharing memory. Yes, it's completely different from what most people are used to, but it's a valid paradigm. I'd go look up "communicating sequential processes" and do some reading if I were you.

LOL this is the classic sort of condescension from the Go community that makes the programming languages community rage. There is a lot of irony here because Go is basically founded on an anti-intellectual ignoring of all previous research.

Re:Rustgo: Calling Rust from Go with near-zero overhead by Vendan on Wednesday August 16, 2017 @11:03PM (#15033484)
And coming in and trashing a programming language is any better? I wasn't attempting to be condescending, CSP was new to me when I was starting out with Go. I'm sorry if my attempt to give you a reference point for looking up something that you seemingly didn't understand came across poorly.
Re:Rustgo: Calling Rust from Go with near-zero overhead by kmicklas on Thursday August 17, 2017 @01:05PM (#15038586)
Why do you think I don't understand CSP? These things are not so novel as you would think from the Go community...
Re:Rustgo: Calling Rust from Go with near-zero overhead by Vendan on Thursday August 17, 2017 @11:23PM (#15043305)
Because you seemed to be saying that without immutability, concurrency is impossible?