Suggestion: target specific runtimes instead of JS versions
First advantage is target to browser is native for user than target to js version. Don't need to know what each browser support. Second is ts can transpilate more effective. Some browser can have partially support of next standard. Ts can transpilate unsupported features only.
Posted by XaveScor on Oct 14, 2017, 4:41 PM
Tags
Related issues
- some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
- I think of this as the kiosk economy.
- What a goofy comment.
- There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
- Compose support in WSLc
- [RFC] Roadmap to v2.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
support (Other)
some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
I think of this as the kiosk economy.
What a goofy comment.
There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
Compose support in WSLc
[RFC] Roadmap to v2.0
[Feature]: Add TurboQuant Support for KV Cache Quantization
Support for AGENTS.md and .agents/skills/, the community has been asking since August 2025
Suggestion: target specific runtimes instead of JS versions
First advantage is target to browser is native for user than target to js version. Don't need to know what each browser support. Second is ts can transpilate more effective. Some browser can have partially support of next standard. Ts can transpilate unsupported features only.
Comments (0)
No comments yet. Start the discussion.