2 ms·
srch is defined in search.ts so no, that's not obvious at all. Having a naming convention is no reason not to do proper dependency management. This global appr
by Kiro 10y ago
srch is defined in search.ts so no, that's not obvious at all.
Having a naming convention is no reason not to do proper dependency management. This global approach just obscures things and makes it untestable.
- ClayFerguson 10y agohaha. There is ONE variable that violates the naming convention. srch!=search.ts. I had a reason for doing that but just never changed it back. The code will easily convert to modules if I ever decide to. For now I'm just keeping it simple. (i.e. no circular-reference risk, etc) It's easy to throw rocks at a design, but if you spent a day working in meta64 you'd realize how intuitive it is. Obscure is never the word you'd use.