So you're saying the article is talking about scripts for continuous integration servers. That makes a lot more sense.
I had read the comments here to mean that people still have to toy with scripts just to get their project to compile.
So you're saying that the source -> executable problem is indeed solved for every language. It's the (source control) -> (source code) + (db change scripts) -> (QA Website) + (QA Database) problem that we're talking about. I didn't gather that from the article.
I'm saying that "source -> executable by pressing a button in an IDE" might be nice for developers, but is utterly irrelevant overall, because you need to be able to build the project without that IDE for lots of different reasons. CI is one, another (most relevant to autoconf) is allowing people to build the project on multiple platforms where the IDE may not even exist.
I had read the comments here to mean that people still have to toy with scripts just to get their project to compile.
So you're saying that the source -> executable problem is indeed solved for every language. It's the (source control) -> (source code) + (db change scripts) -> (QA Website) + (QA Database) problem that we're talking about. I didn't gather that from the article.