upvote

points

by vips7L5 hours ago |
comments
upvoteby gleenn3 hours ago|
[-]
Clojurescript not ClojureJs, and Typescript doesn't run in the browser, it has the exact same issues/limitations: it must be compiled to JavaScript first.
reply
upvoteby vips7L10 minutes ago|
parent|
next
[-]
Except TS has much wider community support. The type definitions/wrappers are already written.
reply
upvoteby warpech3 hours ago|
parent|
prev|
[-]
Compiling TypeScript is just stripping out types
reply
upvoteby gleenn11 minutes ago|
parent|
next
[-]
Isn't that like saying the Internet is only written in English if you strip out all the non-English. All C-style languages are fully cross compatible if you only use semicolons.

I can't write Typescript into a browser without cross-compilation and "stripping out types" involves parsing and manipulating code. That's a different language.

reply
upvoteby Stratoscope2 hours ago|
parent|
prev|
[-]
That is true only if you confine your TS code to be pure JS plus type annotations.

There are TS constructs that require compilation into equivalent JS, such as enums and namespaces.

reply
upvoteby hermanradtke2 hours ago|
parent|
next
[-]
Are there any other?

Namespaces are heavily discouraged. Some teams still use enigma but most people in the know us unions of strings.

I know the TS team regrets enums and I have not seen any plans for adding additional keywords that break type stripping.

reply
upvoteby Stratoscope1 hours ago|
parent|
[-]
The other one I read about was parameter properties in constructors.

And thank you for the correction! It was quite a few years ago that I used TypeScript, and I think the landscape was different then.

Making things even fuzzier in my mind, this was an Angular project, and it was hard to keep track of what was Angular and what was TypeScript.

It sounds like people these days actively avoid the parts of TypeScript that require translation into different JS code.

reply
upvoteby p_l2 hours ago|
parent|
prev|
next
[-]
"fortunately" we can load swc compiled to wasm to deal with that.
reply
upvoteby igl2 hours ago|
parent|
prev|
[-]
absolutely nobody used those outside of a language demo. We also got --erasableSyntaxOnly last year to remove them from the language. The TS team considers them “mistakes“ for a really long time now
reply
upvoteby Stratoscope57 minutes ago|
parent|
[-]
Thanks for the correction! It was a long time ago that I used TypeScript, and making things worse (for my memory) it was an Angular project.

So today, most people and teams avoid the parts of TS that require compilation into different JS, and --erasableSyntaxOnly lets you enforce this, right?

reply
upvoteby igl26 minutes ago|
parent|
[-]
Exactly. There is plenty of code change however introduced by bundlers who do “bundling“, polyfill injection, minification, this kind of stuff.
reply