That's just... ugh. Who thought ordinal numbers were a good idea for plan ids / instance types? Seems part of what you are paying extra for with AWS/GCP etc is competent engineering.
The obvious alternative would be to make the plan IDs reflect the resource limit, e.g. 1024, 2048, 4096, etc.
But that doesn't work with Linode plans because they keep increasing the resources every now and then. They doubled the RAM on all the low-end plans a couple of years ago. Before that, they doubled the storage.
Another option would be to use random IDs that point to a specific bundle of resources. But then the plans change, and the previous bundle is no longer available for purchase.
It's hard to use consistent identifiers when the resources they point to change so often. Linode customers absolutely love those free upgrades.
But that doesn't work with Linode plans because they keep increasing the resources every now and then. They doubled the RAM on all the low-end plans a couple of years ago. Before that, they doubled the storage.
Another option would be to use random IDs that point to a specific bundle of resources. But then the plans change, and the previous bundle is no longer available for purchase.
It's hard to use consistent identifiers when the resources they point to change so often. Linode customers absolutely love those free upgrades.