tristanhoy

3 ms·

1. 1.▲
   by tristanhoy 1y ago

   wasm-bindgen generates a lot of marshalling code on both sides with dynamic allocations and this kills performance. For low-level algorithms, this means that JS + wasm-bindgen will only be marginally faster than pure JS - the overhead of cr
2. 2.▲
   We built a faster WASM-bindgen (2.5×) for high-frequency JavaScript<–>Rust calls(github.com)

   3 points by tristanhoy 1y ago|3 comments
3. 3.▲
   by tristanhoy 1y ago

   A few years back we tried moving our in-memory database engine from Typescript to Rust but found the prototype gains were pretty much deleted by wasm-bindgen because of the high call frequency in our setting. Moving more of our stack into R
4. 4.▲
   The false economics of democratized identity(blog.tokenize.io)

   3 points by tristanhoy 9y ago|0 comments
5. 5.▲
   by tristanhoy 9y ago

   And that's what's so hilarious about putting a content hash on a blockchain, when you can just give it to someone over HTTPS. The hash is plenty immutable all on its own. Strong transaction ordering can give you proof of existence
6. 6.▲
   by tristanhoy 9y ago

   Exactly, it's a tamper proof P2P file system. But it's far from immutable. Torrents die every day because people stop hosting them. The best thing you can do to keep an important but unpopular file alive is ongoing upkeep: host it