4 ms·
Are we just ceding Javascript to Microsoft at this point due to the ubiquity of Typescript?
by dreyfan 5y ago
Are we just ceding Javascript to Microsoft at this point due to the ubiquity of Typescript?
- pjmlp 5y agoIt wouldn't be a loss if browsers could natively understand Typescript annotations, and even take advantage of them for the JIT. Looking forward to the day, actually.
- threatofrain 5y agoIt’s already mainstream to minify your JS anyway as part of a long build process. JS transparency is used by very few people.
- frosted-flakes 5y agoTypeScript does not output obfuscated JS. The output is completely human-readable, even if certain things don't match the source exactly. TS explicitly tries to stay in line with JS, syntax-wise.
- IceDane 5y agoThis is just plain nonsense and is bordering on being paranoid and delusional behavior similar similar to what you'd see from conspiracy theorists. If you ever tried looking at the compiled code, or tried playing with the settings, you can see that typescript is able to output code which is nearly your original code copied, just without types. It all depends on which compilation target you choose. If you choose es3, it will be full of polyfills. If you choose esnext, it will be basically your code.
- eyelidlessness 5y agoIf anything, TypeScript is quite deferential to TC-39. Microsoft is part of the standardization process, but certainly not the main/only driver. I don’t know where you got the impression that this is a MS issue, but TS changes because JS changes not the other way around.
- IshKebab 5y agoNo. Typescript is really strict about being only type annotations for JavaScript (except `enum`), so I'm not sure why you'd think that makes them control JavaScript.