there is no coding principle that more violently combines good-when-used-how-it's-meant with horrible-when-overgeneralized than "explicit is better than implicit" if you're defining a constant DEFAULT_FOR_WHATEVER then every call to some method has to pass that, just fuck you
-
-
yes hello this is $_POST and I'd like to talk to your manager
-
i have no idea what you mean, sure it's exactly like $_POST but it's not in a weird more-global-than-global variable, it's in a nice well-behaved object being explicitly passed instead, and therefore nice and good and beyond reproach
- 1 more reply
New conversation -
-
-
The problem I’ve had with well-definedness in the past is that things are well-defined at time t, and well-defined at time t', … & all these various well-defined-nesses are always present simultaneously later
-
Got me to “static typing is great, for things you build in one consistent compilation run”; seems to be considered gauche these days.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.