4 ms·

very depressing when for so many use cases even native performance is very very very much not fast enough

• Dylan16807 5y ago
  > when If native performance is "very very very" not fast enough then that's supercomputer work and it doesn't really matter if WASM is 3x native or 0.3x native. So that context should be where you're the least depressed.
  • jcelerier 5y ago
    > then that's supercomputer work today's laptop work is late 90's supercomputer's work (and it was even more depressing back then).
    • Dylan16807 5y ago
      And today's supercomputer work was impossible in the late 90's. That doesn't really change my argument. When you're looking at languages that are used for small tasks today, their speed doesn't have much relevance to how vastly bigger tasks are accomplished. And by the time those tasks can be run on a laptop, WASM implementations are going to be much better and we still might not be using it at all for those larger tasks.
• kevingadd 5y ago
  In many of these use cases native is only "not fast enough" because the code you're running makes very poor use of the cache, pipelining, simd instruction sets, and memory bandwidth