News for hackers. Stuff that matters.

A comment on Linux Namespaces and Go Don't Mix. Parent comment

Re:Linux Namespaces and Go Don't Mix by pencilhappen on Friday June 02, 2017 @07:52PM (#14474075)
async/await still has the fundamental problem of composability that all the other attempts at sugaring around an event loop have (aka the "functions have colors" problem [1]). It sucks for collaboration, which is one of the most important things for modern software development.

1. http://journal.stuffwithstuff.com/2015/02/01/what-color-is-y...

[ Parent | on HN ]
Re:Linux Namespaces and Go Don't Mix by pcwalton on Saturday June 03, 2017 @07:14PM (#14479016)
I don't like that article, because (1) it claims Go is doing something new, while Go is really just threads with a particularly idiosyncratic implementation; (2) it ignores the fact that you can convert async to sync by just blocking and sync to async by proxying out to a thread pool. The "what color is your function" problem really isn't a big deal.
[ Parent | on HN ]
Re:Linux Namespaces and Go Don't Mix by pencilhappen on Wednesday June 07, 2017 @03:49PM (#14509358)
A thread pool is far from "ergonomic", it's accidental complexity with numerous gotchas.
[ Parent | on HN ]