It sounds kind of funny to say “this should be in a config, not in code, but here’s a config language that lets you code your config”.
Regardless, I don’t think Dhali was around at the time Quirks.cpp was created.
Funny story, my first exposure to ruby was using it to write ant (or was it maven) config files (EJB nightmares) because the XML config sucked pretty bad (around Rails 1.0 era). It was far more concise and easy to work with, being an actual language and English readable, but I was never sure it was a good idea in a large team environment. If Java hadn’t been so cumbersome I would have used it for config as well instead of the hot garbage XML config was (is still?). I’ve seen a bajillion attempts at config languages since then. Most not great.
A lot of times 2 variables and a `map` function is all I wanted and the config would have been pleasant. Getting type errors in my editor and being able to extend record defaults was the cherry on top.
Regardless, I don’t think Dhali was around at the time Quirks.cpp was created.
Funny story, my first exposure to ruby was using it to write ant (or was it maven) config files (EJB nightmares) because the XML config sucked pretty bad (around Rails 1.0 era). It was far more concise and easy to work with, being an actual language and English readable, but I was never sure it was a good idea in a large team environment. If Java hadn’t been so cumbersome I would have used it for config as well instead of the hot garbage XML config was (is still?). I’ve seen a bajillion attempts at config languages since then. Most not great.