3 ms·
> They are just not something anyone should be using nowadays. I guess it depends, take Vim for example: been around since the early 90s, the developers are fa
by arp242 5y ago
> They are just not something anyone should be using nowadays.
I guess it depends, take Vim for example: been around since the early 90s, the developers are familiar with autoconf, and it seems to work well for them. Why fix something if it ain't broke?
Switching build systems is not necessarily an easy task. Also, as a user I always found cmake quite hard to deal with. Actually, as a user, I actually prefer autotools in spite of its shortcomings. I think there's still quite a bit to win here.
Either way, I personally wouldn't really call autoconf "terrible".
- rsj_hn 5y agoIt's like the saying "the shortest path between two points is the one you know" - the simplest build system is the one that exposes the least complexity to you, which is usually the one that is already deployed and working to your satisfication.
- eru 5y agoUnless you want to make a change or fix a bug, that is.
- eru 5y agoWell, cmake ain't exactly my favourite piece of software either. And, yes, switching an existing system is a different proposition from starting from scratch. Though see what the Neovim people have been doing to remove some of the accumulated cruft from Vim, if you are interested.