Well that’s silly. If the portable options can do it for you, use those.
What I personally find silly is every service rolling there own protocol making it harder for clients to use existing libraries to talk to them and making more work for themselves to get to a quality IPC solution. It usually just ends up in getting something half baked.
There’s nothing inherently “proper” to using platform specific options, but perhaps that’s not even the issue here. It’s a beginner tutorial. A “concise overview of various IPC techniques” with examples that “should compile anywhere a good Unix compiler is available.” What you’re talking about isn’t part of the mission.
Not to mention that just because you're only developing for Linux doesn't guarantee you'll have Binder or D-Bus.
Yes, which is why I highlighted that it is incomplete if you are not limiting yourself to just POSIX. It's important for readers to understand the scope of what is contained in the guide as it would be easy to think this is all the IPC mechanisms Linux offers.
>developing for Linux doesn't guarantee you'll have Binder or D-Bus
This is technically true, but everywhere Linux is used will likely already have one of them: embedded, mobile, desktop, server, etc. For D-Bus you can even have it work in a peer to peer mode where you don't need the daemon.
D-Bus is how XDG and Red Hat software gets onto a Linux system. Without dbus, lots of software with braindead design can stay off of your machine.
PIDs, sockets, FIFOs, and other similar constructs can achieve IPC just fine.
Just as you shouldn't let a crop go monoculture, your software should not all be built on one or two pieces of tech.
What happens when dbus is replaced? Now you have to move onto the new, broken thing, and change your code to adapt, giving control to others over your program.
There are valid reasons to not just cargo cult dbus.
https://0pointer.net/blog/the-new-sd-bus-api-of-systemd.html