Re: Upcoming time boundary events

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