[jitl]

Why would I use this instead of make? I read a bit of the guide to “beast files” here and haven’t seen anything different from make other than some slight syntax differences. https://gauravdawra.github.io/Beast-docs/mainDocs/writingABe...

You should make your value proposition clear in your project README, especially if your syntax and overall model appear to be quite similar to an existing tool. Saying you focus on “ease of usability and speed” doesn’t tell me much.

[gaurav1804]

Hi! I know I haven't supported my claims in the readme. But if you see the syntax for beast build files, you will see that indeed syntax in beast is much simpler and intuitive. For example, you have strings and integers for variables. You can dereference them easily and even create new variables of any type from other variables. You can declare variables inside a build rule. All in all, the syntax is inspired from python, since everyone loves it so much. This is not all, I'm currently benchmarking Beast. The new release: Nimble is turning out to be way faster than Make and even matching/overtaking Ninja (currently one of the the fastest build systems in the community) But you are right in saying that I should include this in the readme. I will surely post this after the benchmarks

[rkangel]

I haven't used Beast, but I have used make a lot. One answer might be "just in case someone wants to put a space in a filename, or in any parent folder of where my code is".

Make does not cope with this at all. Yes I'm aware of all the workarounds and they all fall over at some point. Make works perfectly well on Windows for instance, except for the whole generation of Windows that had the users under "Documents and settings". Was almost always impossible to build code in the user home directory.