From mboxrd@z Thu Jan 1 00:00:00 1970 Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.ada Subject: Re: systemd controversy Date: Wed, 20 Mar 2024 03:17:48 -0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 20 Mar 2024 03:17:48 -0000 (UTC) Injection-Info: dont-email.me; posting-host="a3c7bb3811b3cbef9d335e33aa837a41"; logging-data="1360093"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/Y210e4M7g9NrtH2zyN33v" User-Agent: Pan/0.155 (Kherson; fc5a80b8) Cancel-Lock: sha1:lcLbGcTGt9DgyNTdn1XIqcNOgAo= Xref: news.eternal-september.org comp.lang.ada:66147 List-Id: On Wed, 20 Mar 2024 00:58:30 -0000 (UTC), Kevin Chadwick wrote: > On Tue, 19 Mar 2024 22:29:50 -0000 (UTC), Lawrence D'Oliveiro wrote: >> >>Scripts need an interpreter. Being Turing-complete, in general >>information cannot be extracted from them except by running them. Unit >> files have a fixed vocabulary of keyword entries, which can be easily >> enumerated, looked up, whatever. That’s what’s meant by “declarative”. > > Sorry but that is nonsense. The code behind those unit files is a lot of > disparate C. That’s purely down to how you choose to implement it--it has nothing to do with the format--and meaning--of those unit files themselves. Nobody can stop you from writing bad code to parse a good format. > In my experience init scripts are made entirely of simple commands that > are documented and editable, piece by piece. sysvinit scripts are full of boilerplate sections that users regularly copy and paste from one to the next, without thinking too much about what they do.