3 ms·

Are we making lists? Can we talk about bake (https://github.com/esrlabs/bake https://github.com/esrlabs/bake), bake (https://github.com/linuxrocks123/bake https

Are we making lists? Can we talk about bake (https://github.com/esrlabs/bake https://github.com/esrlabs/bake), bake (https://github.com/linuxrocks123/bake https://github.com/linuxrocks123/bake), bake (https://hackage.haskell.org/package/bake https://hackage.haskell.org/package/bake), Bake (https://www.openhub.net/p/bake-build https://www.openhub.net/p/bake-build), BAKE (https://www.nsnam.org/docs/bake/tutorial/html/bake-over.html https://www.nsnam.org/docs/bake/tutorial/html/bake-over.html), Bakefile (https://bakefile.org/ https://bakefile.org/), BitBake (https://www.yoctoproject.org/software-item/bitbake/ https://www.yoctoproject.org/software-item/bitbake/), and cake bake (https://book.cakephp.org/3.0/en/bake/usage.html https://book.cakephp.org/3.0/en/bake/usage.html)? Now, granted, only(?) seven of these are build systems proper...

ajmmertens 8y ago
Thanks for highlighting this- yes, there are quite a few other projects named bake. The internet is a big place, and while that means that it's almost impossible to come up with a name that's not already in use, the likelihood of running into each other is also small. In other words: I don't see this as a big problem unless one of the "bakes" becomes really big (like CMake big). So what is the chance of this happening? Lets look at the list you provided: - some aren't (C/C++) buildsystems (hackage::bake, bitbake, cake bake). - some projects are dead (linuxrocks123/bake, openhub.net/bake-build, nsnam.org/bake) - some projects are almost dead (esrlabs/bake) That leaves one active project, which is Bakefile, which is not a build system but a makefile generator akin to premake. Bakefile (not bake) has a very different front-end (a bkl file) and different intent, so the potential for confusion is not big. IMO the internet is big enough for two different projects with a similar name :-) Worst case the similarity in names makes it harder for me to get traction, but that's ok really. For me bake is a means to an end, and by no means the most important thing I'm working on. Would I enjoy it if people adopt it? Sure. But it's not the end of the world if that doesn't happen.

ajmmertens 8y ago

Thanks for highlighting this- yes, there are quite a few other projects named bake. The internet is a big place, and while that means that it's almost impossible to come up with a name that's not already in use, the likelihood of running into each other is also small. In other words: I don't see this as a big problem unless one of the "bakes" becomes really big (like CMake big). So what is the chance of this happening? Lets look at the list you provided: - some aren't (C/C++) buildsystems (hackage::bake, bitbake, cake bake). - some projects are dead (linuxrocks123/bake, openhub.net/bake-build, nsnam.org/bake) - some projects are almost dead (esrlabs/bake) That leaves one active project, which is Bakefile, which is not a build system but a makefile generator akin to premake. Bakefile (not bake) has a very different front-end (a bkl file) and different intent, so the potential for confusion is not big. IMO the internet is big enough for two different projects with a similar name :-) Worst case the similarity in names makes it harder for me to get traction, but that's ok really. For me bake is a means to an end, and by no means the most important thing I'm working on. Would I enjoy it if people adopt it? Sure. But it's not the end of the world if that doesn't happen.