That article is really weak as are most articles on opensource.com (some kind of content marketing site of Red Hat). I recount the following points as someone w

That article is really weak as are most articles on opensource.com (some kind of content marketing site of Red Hat). I recount the following points as someone who has worked with Linux for many years and is using it on the Desktop as well as on servers at work but (or thus) has not lost his sense for reality: - the point of "automation" applies to all Unix-like systems. You probably could do the same with Powershell and pdftk for Windows. - Code connections: I don't even know what this is about. - Existing code: same same, but I guess there's indeed more open source / free software for Linux/Unix systems than Windows. - Direct access to peripherals: You might have access to /dev/video0 but that doesn't relieve you from the intricacies in working with that device. Take a look at https://www.kernel.org/doc/html/v4.9/media/uapi/v4l/capture.c.html https://www.kernel.org/doc/html/v4.9/media/uapi/v4l/capture.... to see if that's such a nice API. Also take a look at this to see if the API on macOS is so much worse: https://developer.apple.com/documentation/avfoundation/cameras_and_media_capture/avcam_building_a_camera_app https://developer.apple.com/documentation/avfoundation/camer... - Abstraction layers: the "conveniences" in Qt and Java obviously are not very Linux-specific. "Whole stacks" like Pipewire are work in progress while the multiverse of Jack, Pulseaudio and Alsa makes every programmer wonder what's the proper framework to use. EDIT: I think Linux is a great platform for programming internet services in a modern Unix (containers, userspace networking, epoll, sendfile, AIO, async_tx, ...) way but that's not in the article.