Having some experience porting software to embedded architectures, I can tell you that cross compilation can be a hell in autotools projects just as well. In theory it's easy, but all the projects handle it slightly different, or have hacked around autotool limitations in different ways that don't work with cross compilation etc...
And separate object trees is nothing new, all the newer systems don't even mention it as a feature as it's the default (for example, in cmake).
Standard adherence, you could say something for that, though cmake is a standard in a pretty large amount of projects too these days.
Installation/deinstallation. All of the tools support installation and setting install prefix. And nah, half of the time deinstallation doesn't work. I think that's the task of a package manager anyway (or just in case of experimental stuff install into /opt/XXX).
Their arguments are not very convincing IMO. Unlike the rest of the article which is pretty good this is just bikeshedding.
And separate object trees is nothing new, all the newer systems don't even mention it as a feature as it's the default (for example, in cmake).
Standard adherence, you could say something for that, though cmake is a standard in a pretty large amount of projects too these days.
Installation/deinstallation. All of the tools support installation and setting install prefix. And nah, half of the time deinstallation doesn't work. I think that's the task of a package manager anyway (or just in case of experimental stuff install into /opt/XXX).
Their arguments are not very convincing IMO. Unlike the rest of the article which is pretty good this is just bikeshedding.