undefined | Better HN

0 pointsthrw42A8N1y ago0 comments

I need to worry about it if I'm using it in an app. In what job you don't need to worry about what code are you executing? This is the whole point. It makes my job much harder to do, much more hidden and arcane - not worth it to save few characters.

Yes, reflection is a mistake. It's a hotfix for problems caused by OOP. It's not actually necessary.

TypeScript is a good example. Some people write it like Java/C#, with classes, inheritance, reflection, dependency injection. Usually I can get that code down to 20-30% of original size after I cut out the last class (then I forbid the keyword in linter), and none of that is actually necessary or improved the situation.

0 comments

2 comments · 1 top-level

stephenr1y ago· 1 in thread

> In what job you don't need to worry about what code are you executing?

Worry about? Or understand the fine minutia of how every property you fetch or store is handled?

> It makes my job much harder to do, much more hidden and arcane

I don't know how you do your job, but seeing a real (i.e. not a faux property handled by __get/__set) class member's implementation is literally 1 click away in any decent IDE. Clicking to see the potential hooks of a field vs clicking to see the getter or setter (which may or may not even be defined in the same class) is no different.

> Yes, reflection is a mistake. It's a hotfix for problems caused by OOP. It's not actually necessary.

Right. I guess that's why it's applicable to functional programming. To be a hotfix for OOP?

https://www-master.ufr-info-p6.jussieu.fr/2007/Ajouts/Master...

thrw42A8NOP1y ago

Of course it's applicable, it means "I read the data out of my runtime". Doesn't mean it's what you should do. Like GOTO, mutable variables in global namespace, and so on.

j / k navigate · click thread line to collapse