Hacker News Reader

To be portable it's probably best to use the pthreads API for everything, make no additional assumptions, and rely on the user to provide the implementation. Consider what happens when someone is working with OpenMP, CUDA, or similar and attempts to make use of a dependency that in turn makes use of your library. The easier it is to understand the assumptions made by your library the better.

View on HN

I agree with that. I'm just stating that it's contradictory with the project's own principles.

> Program directly against syscalls

It's the very first one of the listed principles. In the paragraph after this title it even says it "must" be the case in italic to insist on it, and there's a footnote to define what they mean, which is very clear in that pthreads should be out according to this principle.

IMHO this primarily demonstrates what ridiculous of a stance "must program directly against syscalls" really is.

I must suspect the author has insufficient understanding of the dynamic linker, TLS memory management, and the vDSO.

Reply on news.ycombinator.com