2 ms·
Because of the naming convention i'm using for namespaces, if I ever decide to convert to modules, adding the import statements will be straightforward and noth
by ClayFerguson 10y ago
Because of the naming convention i'm using for namespaces, if I ever decide to convert to modules, adding the import statements will be straightforward and nothing will even be renamed. The namespaces would simply 'become' modules, without any editing of the implementation. This was not an accident. I designed it that way.
- Kiro 10y agoAlright. It sounds like something you should add to your TODO. What are your thoughts on for example React, Vue or Angular? Any reason you didn't go that route instead?
- ClayFerguson 10y agoI already had modules on my TODO list, implemented it, didn't like it, took it back out, and converted to TS namespaces. I have been waiting for React to emerge as a clear winner before using it. I only use libraries, APIs, languages, databases, etc. that I've concluded will still be around 10yrs into the future. I don't like Angular, and don't know Vue. If React doesn't replicate some future plans Google has for Polymer ecosystem i might try it.