lol. I thought the batch quip would get your attention Still think its a good example though. the syntax of wb borrows alot from batch. and its really very limited in what it can do, relying on external applicants to do even the simplest of tasks such as accepting user input (choice.com). I can't BASH it to much (hehehehe) though. I cut my teeth on it in my MSDOS days and one of my favorits back in the day was Bart's MODBOOT, wich actually helped spiral me into the world of boot disks, starting with UBCD, then UBCD4Win, and finally Winbuilder.
The .ini file is still by choice for writing and storing configurations. Even with its limitations its still the easy choice for maintaining human readable and configurable settings. Don't get me started on XML, and JSON, isn't much better, unless your goal is to pass chunks of data around.
Like the author said, its a big job to redo a scripting language and my main point wasn't to start a big debate on what is good/bad or BASH (hehehe I did it again ) winbuilders scripting language again as much as we all love it.....Rather I just want to make sure the focus is on making things better, not just making a fancy new car with a bigger motor for the same cockroach to drive around it. Naturally you first have to convince the cockroach that he should try the chevy vs the ford, and making the controls similar so he can just crawl in and start driving is a good way to get him to take a test drive.
As for the reboot offer? If the author wants, I say go for it. Why not. There are still good people there. There are good people at the Oven as well, however make sure you don't call the "command-set formally known as a .script " something other then the word "plugin" or some equally ridiculous offense or you risk being banned.