We rewrote our Rust WASM Parser in TypeScript – and it got 3x Faster

Re:We rewrote our Rust WASM Parser in TypeScript – and it go... by Someone on Saturday March 21, 2026 @02:47PM (#47469999)

> Just pick Python and move fast, kids. It doesn’t matter how fast your software is if nobody uses it.

The reason nobody uses your software could be that it is too slow. As an example, if you write a video encoder or decoder, using pure Python might work for postage-stamp sized video because today’s hardware is insanely fast, but even, it likely will be easier to get the same speed in a language that’s better suited to the task.

[ Parent | on HN ]

Re:We rewrote our Rust WASM Parser in TypeScript – and it go... by wiseowise on Saturday March 21, 2026 @02:59PM (#47470118)

Learning that it’s too slow takes users.

[ Parent | on HN ]

Re:We rewrote our Rust WASM Parser in TypeScript – and it go... by casey2 on Saturday March 21, 2026 @08:53PM (#47473228)

They were the users and it was too slow for them so they switched to python. Not C++ of course, what they meant was "the libraries we wrote in C++ were too buggy and slow that using them was slower than if we just used Python."

[ Parent | on HN ]

Re:We rewrote our Rust WASM Parser in TypeScript – and it go... by Someone on Sunday March 22, 2026 @03:18AM (#47475215)

In some cases, common sense of developers can do that, too.

[ Parent | on HN ]