Hacker News Reader

>Not necessarily just number crunching optimizations

JavaScript is not the language for that objective anyway. So, No!

It's all about I/O.

This is for a client application that is storing a bunch of plain text in a specific format, where the parsing would happen on a separate worker. If you have any advice for how to make faster JS or for how to learn HTML/CSS/JS interop with those things I’d appreciate it. Otherwise it’s not very helpful to just tell someone “JS is not for performance! No!”. As much as people dunk on JS, you CAN write performant code in it. Like there’s been some decades of work put into making it run faster or be able to make games or something in it...

This is going to be platform-specific to a degree. I'd expect there to be profiling tools around V8 and Spidermonkey that can help you figure out what the interpreter makes of your code, and potentially guides on what patterns to avoid. With JITed interpreters, these things can surprisingly specific.

I guess that sentence got a bit too imperative.

Regarding games, it uses subset of OpenGL API. You can use that to crunch numbers actually.

Anyways you'll have to use some external API/FFI for your job.

Reply on news.ycombinator.com