I have. And then I learned that I also need autoconf/automake/m4 (which the author is not mentioning). So there is complexity already out there (even for makefiles)
>server applications ship entire operating systems in glorified chroots;
If this is about Docker, I don't think that the author truly knows how Docker works.
Make is well on its own, especially for everything that is not portable C.
>server applications ship entire operating systems in glorified chroots;
- Docker containers are running chroot'ed
- Containers still do have an whole POSIX-ly userland with shell and coreutils. You can extract every container onto an disk and make an static linux kernel boot it.
- Containers still do have an whole POSIX-ly userland with shell and coreutils.
You can extract every container onto an disk and make an static linux kernel boot it.
Do you have examples of non trivial projects that use only Makefiles and nothing else as a build system?
Its a messy pile of rules tho, but easy to hack some more stuff in or just generate a quick rootfs.
Beside from that, i remember the syslinux bootloader being that way. The linux kernel, busybox and the buildroot distribution also use kconfig, which is Makefile with some config engine in C. If you maintain packages for a distributions, you see what other stuff is used instead of autotools.