Hacker News new | past | comments | ask | show | jobs | submit login

Why is JS bad at "what it tries to do"? I've honestly not seen answer in these discussions, even though everyone acts like they are obvious.

From my experience main problems seem to be:

1) poor static analysis of code, leading to bad Intellisense etc. - Mostly solved by TypeScript.

2) DOM manipulation APIs. I don't see how Rust will help here. Especially considering JS frameworks solve this. I guess that's what's new in the OP.

Otherwise JS serves as pretty good language for beginners/UI wiring.

But thanks for at least describing some strengths (and weaknesses) of Rust when directly compared with JS.




> poor static analysis of code, leading to bad Intellisense etc. - Mostly solved by TypeScript.

Typescript is not Javascript. Most people would agree that that Typescript is a reasonable language.

The fact that it can be transpiled to Javascript is irrelevant, many languages can be transpiled to Javascript.


Well it is still mostly JS. Claiming JS is crap (often stated as "beyond repair") and TS is good just because of (arguably) light addition shows some serious cognitive dissonance. But nevermind:

> The fact that it can be transpiled to Javascript is irrelevant

It has nothing to do with JS, right? :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: