Hacker News Reader

> I worry what else is lurking in libc++ implementations that implies dependencies on things that aren't exactly portable...

You do realize that the C++ runtime library is always a system or compiler supplied non-portable library?

Just like the C library is also highly non-portable. It uses system-specific syscalls all over the place.

> the dependence on /dev/urandom as an absolute path is the most jarring to me.

Why? You use the system supplied entropy source; for each implementation it will use the appropriate one for the platform.

All stuff that communicates with an operating system is non-portable. libc++ is an implementation for Linux/FreeBSD/macOS. /dev/urandom works on all these platforms.

Why does a platform specific compiler need to produce portable binaries?

All I got was "Error establishing a database connection" which does seems like Modern C++ Sausage. Other languages would probably use connection pooling to reduce the number of connections required. /s