4 ms·

Hey FWIW I'm aware I'm more or less trying to hijack a release thread with my gripe. I don't think this should be standard practice for FOSS. In my defense th

Hey FWIW I'm aware I'm more or less trying to hijack a release thread with my gripe. I don't think this should be standard practice for FOSS. In my defense though, I waited for years on this bug, I like TypeScript, I want to use it and evangelize it, and this (pretty fundamental) bug has languished meanwhile we got... module types? I'm pretty sure 99.9999% of devs will never use those. I bet they use iterators though. Also I already have a job, and TypeScript is a Microsoft product with many Microsoft engineers working on it every day. Let's not portray it as entirely the altruism of some saintly engineers donating their time. We're not talking about OpenBSD here.

mattbierner 8y ago
Always remember this: you have different priorities than other users, than other contributors, and than the core team. I for example find import types useful for lazy loading modules, while I’ve never run into this bug in years of writing TS. If there is a bug or feature that really matters to you and that you feel is not being prioritized: - Contribute a fix - Convince someone to contribute a fix - Complain enough that someone contributes a fix (which shouldn’t work but sadly often does) Otherwise it will be fixed when it is fixed. (I am biased because I work with the TS team. However this is just general open source stuff, I’m not speaking professionally)
- camgunz 8y ago
  Sure, that's good advice. But all that stuff already happened here except for "complain enough". Also I didn't realize lazy loading was a common need. Does that mean that awkward syntax is going to be everywhere? Surely there's a better way to get that, like with an import lazy keyword. Really anything would be better.
  - WorldMaker 8y ago
    The `import<TModule>(url: string): Promise<TModule>` syntax/special function was what the TC39 committee agreed to for lazy/dynamic imports after much bikeshedding. It's a Stage 3 ES proposal [1], which means it is likely in the next ES spec version, and is already supported in some browsers and many tools (such as webpack). [1] https://github.com/tc39/proposal-dynamic-import https://github.com/tc39/proposal-dynamic-import

mattbierner 8y ago

Always remember this: you have different priorities than other users, than other contributors, and than the core team. I for example find import types useful for lazy loading modules, while I’ve never run into this bug in years of writing TS. If there is a bug or feature that really matters to you and that you feel is not being prioritized: - Contribute a fix - Convince someone to contribute a fix - Complain enough that someone contributes a fix (which shouldn’t work but sadly often does) Otherwise it will be fixed when it is fixed. (I am biased because I work with the TS team. However this is just general open source stuff, I’m not speaking professionally)

camgunz 8y ago
Sure, that's good advice. But all that stuff already happened here except for "complain enough". Also I didn't realize lazy loading was a common need. Does that mean that awkward syntax is going to be everywhere? Surely there's a better way to get that, like with an import lazy keyword. Really anything would be better.
- WorldMaker 8y ago
  The `import<TModule>(url: string): Promise<TModule>` syntax/special function was what the TC39 committee agreed to for lazy/dynamic imports after much bikeshedding. It's a Stage 3 ES proposal [1], which means it is likely in the next ES spec version, and is already supported in some browsers and many tools (such as webpack). [1] https://github.com/tc39/proposal-dynamic-import https://github.com/tc39/proposal-dynamic-import