Those webdevs are probably simply not used to typing structures. TS Enums aren't a great implementation but certainly not something I'd avoid using or the likes. It's worth taking everything webdevs say about structuring with a big spoon of salt because, with JS being the wild west that it was, most people who work on the web are used to organizing in unique ways and tend to describe normal structuring as clunky, unnatural, weird, bloat or bad.
And it doesn't really matter how they're implemented. An enum is nothing else conceptually than a convenient way to assign a unique value to a variable and organize said variable. You can pretty much 1:1 replace an enum by a string dataclass / array / dictionary in any language you please and not have any real issue in the long run. Enums aren't honestly any major issue, challenge with this codebase. The main issue is that it's just not programmed efficiently - not in terms of language or datastructures, but in terms of algorithms that are o(n^n) opposed to o(n^2) or o
. It's ridiculously inefficient.
