Hi Casper,
thank you for the effort putting things together. I was asking myself
some questions. What is the target group? What is the exact purpose of
that document?
For systemd I have a more practical approach to discuss:
1) how many config statements are there?
2) how many cases exist, which you have to work around (practical
setups, where a config statement is missing or do the wrong thing)
3) how many bugs/feature requests are opened over time and how long does
it take to solve them?
4) how big is the memory footprint and for which systems this is too
much?
5) how many lines of code?
So you would have metrics - especially if you compare them to other
solutions. If you want to have more food, make more metrics (call graph
complexity or whatever). But there are simple metrics, which shows the
result(!) of the design. Talking about the design itself is really a
personal opinion otherwise and very lengthy and needs a lot of
knowledge to follow.
For the philosophy itself there are some parts missing in my opinion:
what does that really mean what you're talking about in practical
solution?
Is there a practical approach anywhere, interface definition,
architecture? You describe a few patterns ok - but they are really
common. I don't get really, which people would help this document.
Maybe that thing is missing: if somebody would like to build a modern
UNIX: what are practical steps to achieve it?
Which tools, which interfaces (kernel, userland) are needed?
Best Regards
Oli
BTW: I can't really see images inside the PDF
--
Automatic-Server AG •••••
Oliver Schad
Geschäftsführer
Turnerstrasse 2
9000 St. Gallen | Schweiz
www.automatic-server.com | oliver.schad_at_automatic-server.com
Tel: +41 71 511 31 11 | Mobile: +41 76 330 03 47
Received on Sun Oct 13 2019 - 08:21:13 UTC