4 ms·
By force, we shall bring type safety to the hellscape that is browser-land! Disclaimer: I am a Rust developer who targets the web.
by evrimoztamur 3y ago
By force, we shall bring type safety to the hellscape that is browser-land!
Disclaimer: I am a Rust developer who targets the web.
- shepherdjerred 3y agoIf you're looking for type safety, isn't TypeScript enough?
- m00x 3y agoTypescript isn't a very strong type system. At least not like Rust/Go are.
- shepherdjerred 3y agoStrong or weak typing doesn't have an impact type safety. TypeScript is statically typed which guarantees type safety. TypeScript is often used in web environment which often leads to developers defeating the type system. For example, applications often cast some user input, API response, or local storage to an expected type, but that is not a limitation of TypeScript, and would not necessarily be solved by using some other language like Go or Rust. TypeScript is an unsound type system [0], but in practice this doesn't have any real impact on most web applications. [0]: https://www.typescriptlang.org/docs/handbook/type-compatibility.html https://www.typescriptlang.org/docs/handbook/type-compatibil...
- graypegg 3y agoInteresting, strict + static types in Rust isn't normally what most Rust people are proud of, it's normally the memory safety guarantees. The web isn't a hellscape, but I'm still hyped about WASM on here!
- Conscat 3y agoThe memory safety guarantees are: Rust has affine _types_ ^. ^ With opt-in memory leaks