←back to thread

517 points bkolobara | 7 comments | | HN request time: 0.206s | source | bottom
1. phplovesong ◴[] No.45050053[source]
This boils down to "dev found out that a static typesystem is usefull".

Its always funny when i see these kinds of posts.

replies(3): >>45050162 #>>45050390 #>>45053842 #
2. bkolobara ◴[] No.45050162[source]
My intention with the blog was to show that Rust's lifetime tracking and trait system allow you to catch much more complicated issues than just "one type doesn't match another" errors.

That's the main reason why I chose to compare it with TypeScript, that is also a statically typed language, but just can't catch some issues that Rust can.

replies(2): >>45050377 #>>45054951 #
3. Tryk ◴[] No.45050377[source]
The notion of a type is not fixed, Rust has a more generous conception of what is a type and what its static type system checks.
4. ◴[] No.45050390[source]
5. wmanley ◴[] No.45053842[source]
> Its always funny when i see these kinds of posts.

What's funny about it?

replies(1): >>45054894 #
6. phplovesong ◴[] No.45054894[source]
Basically that you list the obvious benefits we knew since the 70s (in a new blogpost).

Its a form of re-discovery, and im happy people "find" the joy of it.

Rust borrows heavily from the other ml's and thats why many like it, not realizing there is decades of research behind the whys.

7. phplovesong ◴[] No.45054951[source]
The bug you showed had nothing to do with typescript (JS) but the browser API. Typescript is not a good languge, but still a way better option than vanilla JS.

I kind of wish Haxe would have taken TypeScripts place as it is simply a better language overall.