Thats OOP, we don't do that anymore!!! /s

> For example, I don't ever see anyone using `dynamic` or `object` in C#

I have bad news for you

Is your bad news that you primarily have to work in bad codebases? If so, sorry to hear that.

On my last Japan vacation I actually managed to gain weight

I moved to Japan 7 years ago and managed to gain 10 kilos. It is nowhere as healthy as people say.

> however someone made a validator that resolves the logic to a specific class at runtime. So you'd basically have validator.validate(Object someObject).

The pains of not having multiple dispatch.

And yet we don't. Curious!

> If I have a fruit which is an apple or a banana, I can't pass that to a method expecting an apple or banana. It can only be passed as a fruit.

You can by overriding the method on apple or banana. If your method is on some other object, then yes, you cannot do this unless your programming language supports multiple dispatch.

It's both hilarious and sad to see a bunch of 30-40 year old open source devs with mentalities comparable to Reddit moderators collectively bullying a 20(?) year old slightly immature dude.

If they were Reddit moderators they would have banned the trans person for being trans.

Dynamic scope is still very useful for some things. But it's certainly way over-used in a lot of the old Emacs libraries for example.

I could just as well argue that those families have better genetic material and that is why they are wealthy.

Except without any of the good parts of historic feudalism.