Maybe you don't need Rust and WASM to speed up your JS

Re:Maybe you don't need Rust and WASM to speed up your JS by Animats on Monday February 19, 2018 @12:29PM (#16414215)

Source maps are a debug tool. Why does the performance matter?

(And if you're shipping so much JavaScript to your site users that you need to "minify", maybe you're doing it wrong.)

[ Parent | on HN ]

Re:Maybe you don't need Rust and WASM to speed up your JS by orf on Monday February 19, 2018 @12:36PM (#16414254)

Tools like Sentry parse them, and need consistent fast performance in this area. Other debugging tools use them.

Your statement in brackets seems very "those damn kids"-ish. You need to "minify" your JS files even if you're shipping a small amount of JS, because loading performance matters and JS minifies very well.

[ Parent | on HN ]

Re:Maybe you don't need Rust and WASM to speed up your JS by masklinn on Monday February 19, 2018 @01:47PM (#16414744)

Browsers also use them do display "expanded" code in the console and debugger.

[ Parent | on HN ]

Re:Maybe you don't need Rust and WASM to speed up your JS by tromey on Monday February 19, 2018 @12:35PM (#16414249)

> Source maps are a debug tool. Why does the performance matter?

If the source map decoder is slow, then the debugger feels slow.

[ Parent | on HN ]

Re:Maybe you don't need Rust and WASM to speed up your JS by bluetwo on Monday February 19, 2018 @03:38PM (#16415552)

> if you're shipping so much JavaScript to your site users that you need to "minify", maybe you're doing it wrong.

100% agree.

[ Parent | on HN ]

Re:Maybe you don't need Rust and WASM to speed up your JS by bluetwo on Tuesday February 20, 2018 @12:13PM (#16421928)

Make that 101% agree.

[ Parent | on HN ]

Re:Maybe you don't need Rust and WASM to speed up your JS by bluetwo on Wednesday February 21, 2018 @12:10PM (#16430976)

102%

[ Parent | on HN ]