Sujet : Re: Upcoming time boundary events
De : syseng (at) *nospam* gfsys.co.uk (chrisq)
Groupes : comp.os.vmsDate : 10. Jun 2025, 23:33:52
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <102absh$1hjjr$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
User-Agent : Mozilla Thunderbird
On 6/10/25 20:20, Arne Vajhøj wrote:
On 6/10/2025 2:36 PM, chrisq wrote:
On 6/9/25 23:51, Lawrence D'Oliveiro wrote:
On Mon, 9 Jun 2025 17:34:31 +0100, chrisq wrote:
That's interesting, but wonder if they really needed the overarching
complpexity of systemd to enable that. More productive and less
disruptive to build on what is already there, but ymmv.
>
I wonder how you see “complexity” in a unified approach to things, as
opposed to the old different-mechanism-for-each-connection-type legacy
thinking.
>
Good engineering is about minimising complexity as far as is practical,
which reduces design and ongoing maintenance, management and staff
reeducation costs. Fewer possible bugs, as well.
"Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away"
I think it is good engineering.
But it does not reflect the world of software development today. It is
common to have code bases grow 5-10% per year (which means doubling
every 10 years) for relative mature applications and 15-30% per
year (which means doubling every 3 years) for applications in
quickly evolving domains.
Arne
Absolutely, though present Linux does seem to have forgotten that
guiding principle.
Have some old DEC DMCC industrial pcs and sorting though the pile,
found two Alpha processor examples. 21164 cpu, single board
processor, with a passive pci backplane. Thought it might be
fun to resurrect one or both as an exercise, as still have a
Suse Linux Alpha 7.1 distro kit with all cds, which had never
been used here. Around 2000/2001 era. Both had some early
prototype bios, so probably pre prod hardware and firmware,
though good help screens from a serial console. Can be either
floppy or network boot to update the bios, so setup a mop server
on the lab server, FreeBSD, booted via a network card almost
instantly, choose srm, and updated the bios. Found a few
other bits and pieces and now have Suse Linux up and running,
though still have to configure X for a desktop login. Have to
define the graphics card and monitor etc, before it will play,
so not so plug and play, as later versions.
Had forgotten just how professional and fully sorted, Suse Linux
was at the time. In particular, the seamless install process.
Chris