I would agree with you if trixie had just been released, but a lot of the rough edges have been worn off by now. Running the present branch of debian stable (as opposed to debian testing) is already an extremely conservative choice and gets you a lot of revisions of packages that are quite old compared to what ships in other distros...
Trixie is 14 months old now
Hardware doesn't grow younger magically. Upgrading is not always an option, even as a release becomes mature.
> I would agree with you if trixie had just been released, but a lot of the rough edges have been worn off by now.
That doesn't help if you need to run a piece of software only certified to run under a certain Java version or, worse, a certain OS version. It's either "run on something really old" or "lose the ability for commercial support / you're on your own if shit happens".
Yes, but there is software you may rely on that has not yet adjusted to Trixie or if it has you have not had the time/resources to test that upgrade path.
As someone who works in IT around administration of 30+ Debian boxes for a decade now: Updates are easy in theory only or if the software doesn't rely on any OS package. Sure, most updates of well written software are easy, but we also had to manually migrate database schemas and similar things.
How do I best explain this?
I upgraded to Trixie. Stuff broke.
I rolled back to Bookworm, which was extremely painful, because unlike other OSes rollback is not possible and a reinstall is necessary.
Stuff worked again.
Maybe I'll give it another go in 2028 when it goes EOL. Or maybe not. I'm not under any obligation to keep trying.
To give an example, there is a rough edge called Dovecot 2.4 (new config syntax, Director removed, master/master replication removed) that will not wear off by itself. Upgrading to 2.4 could, depending on the complexity of your setup, require days to weeks of planning, testing and implementation.