Journal Journal: AutoConf Sucks 7
I really hate autoconf. Its cryptic, it is a pain in the ass to use, and the only thing its got going for it is that the open source movement uses it like a bunch of lemmings.
I have went to the trouble before to make use of it. I found nothing of value from the experience other then a reminder of what it was like to write code ten or so years ago. Autoconf requires too many steps, its maintenance is high, and finding rule-sets that you need normally involves finding another project (yes I am aware of the archive) and looking to see how they did it. Who really wants to deal with M4 anymore?
What I have in mind is something a bit different. Lets put rule-sets in CPAN (yeah, I know, Perl, boo-hiss, whatever) and create an interface that builds your configure script by asking you a few questions. It should be able to pull whatever modules it needs from CPAN and then bundle them with your application so that it is portable. Have the configure script then generate make files.
Just imagine running a configure script where you will always see the same options. Perl is everywhere. Java may have Sun's marketing behind it, but Perl is the one language that is everywhere and comes on just about everything (and even Microsoft doesn't seem to have a problem with it, I have MS employees in my Perl classes at the University of Washington all of the time).
Autoconf has got to go, its time was nearly a decade ago. There is no reason to keep ourselves tied into this piece of legacy.