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
-
-
Recently had this discussion re: locales (or TZ, …) as a process-wide thing in e.g. web servers. Passing through of all these things entirely impractical, as is creating closures/partials for a hundred functions. Hate thread/request locals.
-
Best I got is something like computing these data from request and memoizing it with a MRU LUT; request as a parameter is usually in scope. Still vaguely suckish, but at least explicit yet up-front practical. Anything nicer?
- 7 more replies
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.