←back to thread

Unexpected productivity boost of Rust

(lubeno.dev)
517 points bkolobara | 5 comments | 27 Aug 25 15:48 UTC | HN request time: 0.873s | source
Show context
gedy ◴[27 Aug 25 17:06 UTC] No.45042251[source]▶
> Assigning a value to 'window.location.href' doesn't immediately redirect you, like I thought it would.

That's not a "Typescript" or language issue, that's a DOM/browser API weirdness

replies(3): >>45042856 #>>45043364 #>>45045727 #
1. love2read ◴[27 Aug 25 18:40 UTC] No.45043364[source]▶
*though it could have been fixed by typescript had they cared.
replies(1): >>45043549 #
2. morcus ◴[27 Aug 25 18:56 UTC] No.45043549[source]▶
How could Typescript have fixed this?
replies(1): >>45044233 #
3. love2read ◴[27 Aug 25 19:48 UTC] No.45044233[source]▶
they could have provided a seperate api over top of this and error’d on use? It’s a clearly error-prone api.
replies(2): >>45044494 #>>45049887 #
4. morcus ◴[27 Aug 25 20:07 UTC] No.45044494{3}[source]▶
I genuinely don't understand - how could Typescript provide a separate API on top of this? I usually do not expect Typescript to start generating code and APIs for me.

Also, Typescript is adding types on top of the JavaScript language, not the DOM API.

5. extraisland ◴[28 Aug 25 08:42 UTC] No.45049887{3}[source]▶
No they shouldn't have done. The Browser API Implementation doesn't exist in TypeScript. It exists in the browser. TypeScript shouldn't be fixing how the browser behaves.

Think about what is happening. When you build to the browser as a target, TSC basically transpiles the TypeScript code to JavaScript. The Browser APIs that Typescript provides are a bunch of type definitions. When it transpiles the code the only thing it can really do is check the types match up.