when writing somewhat low-level code, you always make assumptions about things. in this case, they chose to manage 256 entries in some array; the bound used to be lower.
but implicitly there’s a tradeoff, probably memory / CPU utilisation in the server.
it’s always about the tradeoff between what the users want, what is easier for you to maintain, what your infrastructure can provide, etc.
when writing somewhat low-level code, you always make assumptions about things. in this case, they chose to manage 256 entries in some array; the bound used to be lower.
but implicitly there’s a tradeoff, probably memory / CPU utilisation in the server.
it’s always about the tradeoff between what the users want, what is easier for you to maintain, what your infrastructure can provide, etc.