I saw Sergio giving 
@janneke a live presentation and Janneke seemed absolutely wide-eyed and amazed. I askeed Janneke "well what do you think?" and he said "I'm absolutely hooked".
Well, I can hardly think of many people who would give a more compelling recommendation than the champion of bootstrappability efforts and founder of the Mes compiler used for those same goals. Seems promising.
@cwebberChristine Lemmer-Webber
Cc: 
@shepherdSergio Pastor Pérez
*blush* thanks!
I've looked some more at replacing Autotools with Blue (B.L.U.E.?) for Dezyne (https://dezyne.org) and while we're not there yet (quite possibly due to my lacking Blue skills), it is looking promising, and moreover, it's been real fun!
I have a soft spot for hacking build systems. On the one hand I hate them, but I also really like automization and executable documentation. And I've invested some time in them. But it's always been kind of a fight. M4, Perl, Bash. config.log. Terrible. Also: why??? Then, Cmake came along with it's ridiculous CmakeList.txt, home-grown "language", terrible generated makefiles with absolute file-names, and without any free documentation. Selling *proprietary* documentation as business model. Decided to never touch it! Anyway, now with Blue, we can hack in Guile! ❤️
We wrote a blazingly fast build system based on GNU make for GNU LilyPond, called stepmake, because running autoreconf and automake took 45min. It never took off though. Later, I fully reimplemented LilyPond's build system in scons only to find that after a completed build, it would take "scons build" about a minute to determine that there was nothing to be done. We reverted to stepmake.
Really looking forward to working more with Blue!
If you have a fediverse account, you can quote this note from your own instance. Search https://todon.nl/users/janneke/statuses/116018413027242181 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
