Follow

neverworkintheory.org/ was an awesome blog about actual scientific papers on software engineering. It's too bad it stopped.

@liw Also Greg Wilson is one of the people I miss seeing now that I no longer use Twitter. I need to get back to using an RSS feed reader.

@liw "The Morning Paper" can partially fill the gap:

- a paper about "convoy phenomenon", a peculiar way in which one slow process can leave the whole system bottlenecked even when it's done doing the work: blog.acolyer.org/2019/07/01/th

- a paper about bugs that cause incidents in clouds (applicable to any system IMHO): blog.acolyer.org/2019/06/21/wh

- a paper about how Go's concurrency primitives don't actually lower the number of bugs: blog.acolyer.org/2019/05/17/un

- and many more in the archives.

@minoru @liw

that article about Go's concurrency primitives being bug-prone would be more convincing if it showed examples of other languages where 2.2 million lines of code with 34 bugs is considered a lot.

@ben Okay, sorry, my summary was absolutely wrong: the paper (and the article) compare Go's shared memory primitives with channels, and finds that message passing created more blocking bugs than traditional synchronization primitives. (The outcome is different for non-blocking.)

There are a ton of caveats there; see Section 4 of the paper, "Threats to validity".

Section 8 mentions seven other empirical studies of the same sort; perhaps the answer to your question is somewhere in there.

@liw

Sign in to participate in the conversation
toot.liw.fi

Lars and friends