Hacker News new | ask | show | jobs
by wpollock 32 days ago
> Because "it doesn't exist". It's just a layer on top of js, ...

C++ was originally a layer on top of C. The first C++ compiler, "cfront" was actually a transpiler to C.

There is nothing preventing TypeScript from becoming "native" in a similar way.
2 comments
pjmlp 32 days ago
Typescript is only a linter, except for types annotations it is regular JS, quite different from C with Classes.

If you are going to mention enum and namespaces, the team considers them a design error, and only keeps them around due to backwards compatibility.

link
wpollock 31 days ago
> Typescript is only a linter...

I never thought of Typescript (TS) that way. I believe TS is a language addition that enabled smarter JavaScript linters; TS is not a linter program per se.

However, TS is more than that now. The extra annotations enable optimizing transpilers and even compilers (to WASM, for instance). This makes TS much more than just a better linter; I think of TS as a better language.

link
pjmlp 30 days ago
Already covered by JSDoc, closure, and Babel before Typescript came to be.

Java IDEs were taking advantage of them for web development workflows, before VSCode came to be.

Also VSCode main architect is one of the Eclipse original architects.

link
sirsinsalot 32 days ago
It doesn't make any sense tho. Typescript is nothing much to do with runtime. It's a build/dev concern. To get JS from TS you're mostly removing the type annotations.

Theres no reason to ship TS to an end user browser.

link
wpollock 32 days ago
> Theres no reason to ship TS to an end user browser.

As things are now, developers write code in TypeScript, then debug and update code in Javascript. It might not be much of a reason, but a single language throughout is surely easier on developers and maintainers.

link