Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Your comment makes no sense, goroutines are multiplexed on each cores thus it has parallelism.

https://en.wikipedia.org/wiki/Parallel_computing

"Parallel computing is a type of computation in which many calculations or the execution of processes are carried out simultaneously."

Do you enjoy trolling and dismissing Go in general? Reading your comments sounds like some envy toward Go popularity. When you're not complaining about concurrency features it's about Go GC.



And Node has workers and can thus achieve parallelism as well. What matters isn't whether the language can achieve parallelism: it's whether the language is designed for it. Go is designed for concurrency, not parallelism.

It's Rob Pike's view [1] that concurrency enables parallelism "for free". I think that's oversimplified and at odds with the way people who write CPU-bound code actually use parallelism features, but that's how Go was designed: it omits traditional parallelism features in favor of concurrency features.

[1]: https://blog.golang.org/concurrency-is-not-parallelism




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: