Bingo. Everything has a limit and when you set it yourself you’re moving the “how many x can I make?” answer from the “unknown” column to the “known and testabl

Bingo. Everything has a limit and when you set it yourself you’re moving the “how many x can I make?” answer from the “unknown” column to the “known and testable” column. Imagine if you add a feature tomorrow that, on startup, has to run something in linear time with the number of channels you have. If the upper bound were essentially undefined (and not practically testable if it’s max int(32)) it could be that in practice your new feature makes it so that getting above 23,456 channels effectively disables the server due to a timeout in a critical part of startup. But if you’ve defined that channel limit, you can be confident that a feature like that either does or does not break things, even when at your channel limit, because you can test that.