I can't really put a finger on why, but for some reason runtime reflection in programming languages makes me feel slightly uneasy in the back of my mind. It feels like it's both cheating, but it should also be perfectly natural somehow. But it's neither. But at the same time it's also both.
Compile time reflection? Perfectly fine. Makes total sense.
Runtime reflection? Weirds me out every time I use it or see it used. Just that tiny little bit.

@talon

wanted to write a little rant on how reflection and laziness are very closely linked, but technically dlopen and dlsym together are also a kind of reflection. so, not quite so convinced of my own argument any more :dragnmlem:

@dhivael Even in languages that have good reflection support I refuse to use it unless I absolutely have to, because I agree. It ends up in a big mess more often than it helps, and the time you spend figuring out why your random reflection breaks is better spent just avoiding it in the first place I feel.

Listen

@talon

yeah, same. using reflection is tantamount to writing in an untyped fragment, which is ... not great

Sign in to participate in the conversation
Dragon Style

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!