Hacker News Reader

Comment by Jenk | Hacker News Reader

I don't need to "justify" their immaterialness. The OP needs to explain how it is material.

But whatever...

The merits of ES6 are also present in typescript. Thus claim 1 is immaterial.

Claim two is rebuked by intellisense and very strongly argued against in a shared-code world.

Claim 3 is presumptive that TypeScript would be the only transpilation, despite nue itself being a transpiler. In addition to all the other bundling modern products use for treeshaking, minification, etc. This is an insignificant and thus immaterial point.

("justification" enough for you?)

Did you even read the FAQ?

View on HN

Jenk — can you help me with a list of valid reasons to choose JavaScript so that the TypeScript community is pleased? This would help me a lot. Thank you!

My hot take is that you can't reason with a cult.

For me, Typescript is more like documentation combined with Grammarly.

I would love to but I just can't see how it could be done.

I am interpreting the task as "how can we make people who favour strong typing favour not use strong typing?" - something that I just don't think is possible.

I guess the nearest experience you'll get is a zealous API convention that is inuitively consistent/discoverable, but then I would still favour a type system to remove that concern anyway.

The question is more like: "What are the benefits of choosing JavaScript over TypeScript?" You must know that there are pros and cons in every language. There is a reason languages like JS, Python, Zig, C, Go, Rust.. exist.

Given TypeScript is a superset of JavaScript, it's actually a question of "Would you prefer it if we took these (TypeScript) things away?"

I was asking you to take a little distance from the TS-world and use your experience (and maybe emphaty) to look about the pros of JS. Preferrably a list that pleases the TS community. The fact that JS is an "universal language" and runs natively on browsers and Node is a definite one, but then again.. this was a question for you.

The "pros" of JS exist within TS.

1. Proxies are painful to say the least on TS.

2. Code completion can be done also without static typing. Also relying on code completion is a strong smell of a bad codebase. The "very strong arguments" rarely have any empirical basis.

3. Transpilers/compilers are bad and more transpilers are worse. I would prefer a pure browser framework though. A lot of projects would be and are fine without treeshaking, minification etc. And those are practically never needed for development where the compilation step causes most harm.

For someone who opened with an accusation of baseless claims, you haven't done a very good job of providing a basis for your own claims.

Reply on news.ycombinator.com