Probably because many *geeks* find it impossibly arcane to use? make scripts are something that get written once and rarely touched again in many FLOSS projects because no-one can understand them. Many geeks therefore consider make a necessary evil. This gets make reinvented even in contexts that match it's ostensible purpose.
In the circles I develop in (python web apps) for example, buildout recipes are usually used as an alternative to make to take advantage of setuptools, distutils, and easy_install. But still no-one uses it inside a CMS.
Consider that there is an impedance mismatch between running make and it's equivalents (ie. rebuilding everything that has changed) and the desired functionality of many CM systems, which in some contexts need to do things like publish all changes immediately (ie. without waiting for someone to push the big red button), and in others want someone else to approve a change (or set of changes) first, or leave a draft item unpublished indefinitely, or publish something at a future date, etc. In some cases, different projects need different workflows, so it needs to be configurable, even by an administrator, without writing or editing scripts.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2008-01-09 11:33 am (UTC)Probably because many *geeks* find it impossibly arcane to use?
makescripts are something that get written once and rarely touched again in many FLOSS projects because no-one can understand them. Many geeks therefore considermakea necessary evil. This gets make reinvented even in contexts that match it's ostensible purpose.In the circles I develop in (python web apps) for example,
buildoutrecipes are usually used as an alternative tomaketo take advantage ofsetuptools,distutils, andeasy_install. But still no-one uses it inside a CMS.Consider that there is an impedance mismatch between running
makeand it's equivalents (ie. rebuilding everything that has changed) and the desired functionality of many CM systems, which in some contexts need to do things like publish all changes immediately (ie. without waiting for someone to push the big red button), and in others want someone else to approve a change (or set of changes) first, or leave a draft item unpublished indefinitely, or publish something at a future date, etc. In some cases, different projects need different workflows, so it needs to be configurable, even by an administrator, without writing or editing scripts.