Yeah, the problem is not that the dude is type-a (though not sure that’s even the case since he just vibe coded some BS), the problem is he’s a grifter grind-maxer which are distinct things.
Honestly, I think type-A and type-B are WAY to simplified to be useful in any context, let alone diagnosing the problems of humanity.
I disagree, that it is mostly preference. I agree that it has been implemented both ways, but once you get into the scalability question, it becomes clear that passing in an argument cuts down on the logical branching. If you have both an enable and a disable function as your pattern, then for components you need to reason about state for during runtime will need an if/else which can get out of hand quickly when you are driving multiple component states.
Very ironic you are saying that on a federated social media platform with no data centers.
Tell me about it, my rig went up by ~30% and to think I was worried it wasn’t future proof enough