This I think is the main problem to adoption. It’s very hard to come across Lemmy results on a search engine even if I’m trying to specify Lemmy. (Not that search engines matter for most people these days what with the LLM executive summary pushing out real web pages, who needs resources when you have slop, am I right? \s)

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.

Chefs kiss that he is typing in all caps.